Code execution via RAR node-count overflow
Published Jun 9, 2025 · Updated Aug 25, 2026
Memory corruption in libarchive before 3.8.0 allows local users to execute code or crash applications via a crafted RAR archive. The RAR reader lets a node-count multiplication wrap to zero, passes zero to realloc, and later frees the same allocation again. Exploitation requires an application to process a RAR archive containing more than four billion nodes and over 103 GB of available memory.
Summary
What happened
Memory corruption in libarchive before 3.8.0 allows local users to execute code or crash applications via a crafted RAR archive. The RAR reader lets a node-count multiplication wrap to zero, passes zero to realloc, and later frees the same allocation again. Exploitation requires an application to process a RAR archive containing more than four billion nodes and over 103 GB of available memory.
The record
- CVE
- CVE-2025-5914
- Published
- Jun 9, 2025
- Updated
- Aug 25, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat OpenShift Serverless
- Classifications
- CWE-190, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 9, 2025CVE publishedPublication date reported by the CVE source.
- Aug 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Four-billion-node RAR proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo