CVE-2025-5916: Libarchive: integer overflow while reading warc files at archive_read_support_format_warc.c
A vulnerability has been identified in the libarchive library. This flaw involves an integer overflow that can be triggered when processing a Web Archive (WARC) file that claims to have more than INT64_MAX - 4 content bytes. An attacker could craft a malicious WARC archive to induce this overflow, potentially leading to unpredictable program behavior, memory corruption, or a denial-of-service condition within applications that process such archives using libarchive. This bug affects libarchive versions prior to 3.8.0.
Security readout for executives and security teams
Plain-English summary
Libarchive can mishandle a specially crafted WARC archive and overflow an integer while reading it. The likely business impact is localized: applications or systems that process untrusted WARC files may crash, behave unpredictably, or expose limited data. The published severity is low.
Executive priority
Treat this as a routine remediation item unless your organization processes untrusted WARC archives at scale. Prioritize affected ingestion systems, archive-processing services, and shared container images, but this does not appear to require emergency response based on the provided evidence.
Technical view
CVE-2025-5916 is a CWE-190 integer overflow in libarchive's WARC reader, triggered by a WARC file claiming more than INT64_MAX - 4 content bytes. Sources describe possible unpredictable behavior, memory corruption, denial of service, and limited confidentiality impact. Libarchive versions before 3.8.0 are affected.
Likely exposure
Exposure is most likely where libarchive processes WARC files from users, partners, crawlers, archives, or automated ingestion pipelines. The bundle lists RHEL 8, 9, 10 and OpenShift Container Platform 4 as affected; RHEL 6 and 7 status is unknown.
Exploitation context
The CVSS vector requires local access, low complexity, low privileges, and user interaction. The source bundle does not show CISA KEV listing or other evidence of active exploitation, so active exploitation should not be assumed.
Researcher notes
Key boundaries are clear: WARC parsing, integer overflow, versions before 3.8.0, and Red Hat affected-product status. Evidence is incomplete for exploit-in-the-wild activity and for final fixed package availability across every listed Red Hat platform.
Mitigation direction
Upgrade libarchive to version 3.8.0 or a vendor-fixed package when available.
Follow Red Hat guidance for affected RHEL and OpenShift packages.
Limit or isolate processing of untrusted WARC files until patched.
Review container base images and embedded dependencies for vulnerable libarchive versions.
Track RHEL 6 and 7 status if those platforms remain in use.
Validation and detection
Inventory systems, containers, and applications that include libarchive.
Check whether any workflows ingest or unpack WARC files.
Confirm installed libarchive versions are 3.8.0 or vendor-fixed builds.
Review SBOMs for transitive or embedded libarchive copies.
Verify Red Hat package status for each affected operating environment.
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 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.