CVE-2025-5914: Libarchive: double free at archive_read_format_rar_seek_data() in archive_read_support_format_rar.c
A vulnerability has been identified in the libarchive library, specifically within the archive_read_format_rar_seek_data() function. This flaw involves an integer overflow that can ultimately lead to a double-free condition. Exploiting a double-free vulnerability can result in memory corruption, enabling an attacker to execute arbitrary code or cause a denial-of-service condition.
Security readout for executives and security teams
Plain-English summary
CVE-2025-5914 is a high-severity libarchive memory-safety flaw triggered while processing RAR data. A malicious archive could crash an affected process or potentially enable arbitrary code execution. Successful exploitation requires a user or application to process the archive, so systems handling untrusted uploads or attachments deserve prompt attention.
Executive priority
Treat this as a prompt patching priority for internet-facing upload pipelines, mail or content scanners, and shared extraction services. Other systems can follow risk-based scheduling after confirming whether they process untrusted RAR files. There is high potential impact, but no supplied evidence of active exploitation.
Technical view
An integer overflow in archive_read_format_rar_seek_data() can lead to a double free and memory corruption. CVSS 3.1 rates it 7.8: local attack vector, low complexity, no privileges, user interaction required, and potentially high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is highest where affected libarchive packages automatically or routinely inspect attacker-controlled RAR archives, including upload, attachment, scanning, or extraction workflows. The bundle identifies affected Red Hat Enterprise Linux 7–10 variants and OpenShift 4.14–4.16 builds; it does not establish every affected upstream or downstream version.
Exploitation context
The supplied sources do not report active exploitation, and the CVE is not marked as CISA KEV. Exploitation requires crafted input to be processed locally, but no privileges are required. Potential outcomes include process denial of service or arbitrary code execution in the affected process's security context.
Researcher notes
The vulnerable path is RAR seek handling in archive_read_support_format_rar.c. The stated weakness is CWE-190, with integer overflow progressing to double free. The bundle provides affected Red Hat package builds and multiple errata, but no complete upstream affected range, fixed-version boundary, public proof of concept, or confirmed exploitation telemetry.
Mitigation direction
Identify systems and applications using libarchive to process RAR files.
Apply the applicable Red Hat security erratum or current vendor-supported update.
Prioritize services that accept archives from untrusted users or external sources.
Until updated, restrict untrusted RAR processing where operationally feasible.
Check upstream or downstream vendor guidance for products not covered by Red Hat advisories.
Validation and detection
Inventory installed libarchive and RHCOS package versions across hosts, containers, and images.
Compare detected versions and product streams with the applicable vendor advisory.
Confirm updated packages are active after deployment, including rebuilt containers and restarted services.
Review archive-processing workflows for externally supplied RAR content.
Monitor affected processes for unexplained crashes or memory-corruption indicators.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-190: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-190 · source CWE mapping
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.