LiveActive security incident?Get immediate response
CVE Record

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.

LowCVSS 3.9Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

Libarchive versions before 3.8.0 can mishandle a deliberately malformed WARC file whose claimed content size exceeds a 64-bit boundary. Applications processing that file may crash, corrupt memory, or behave unpredictably. The supplied severity is low because exploitation requires access and user interaction, with limited expected confidentiality and availability impact.

Executive priority

Treat this as routine, targeted remediation rather than an emergency. Prioritize internet-facing or automated services that ingest untrusted archives, then update remaining affected systems during normal patch cycles. Escalate if WARC processing is exposed to external users or vulnerable libarchive copies are embedded in critical services.

Technical view

CVE-2025-5916 is a CWE-190 integer overflow in archive_read_support_format_warc.c. A WARC content length greater than INT64_MAX minus 4 can overflow an internal calculation. The supplied CVSS 3.1 score is 3.9 (AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:L). Versions before libarchive 3.8.0 are affected.

Likely exposure

Exposure is most likely where software using libarchive accepts or processes untrusted WARC archives. The bundle marks RHEL 8, 9, and 10 and OpenShift Container Platform 4 as affected. RHEL 6 and 7 status is unknown. Systems that never process WARC files have substantially lower practical exposure.

Exploitation context

The supplied record is not in CISA KEV and provides no evidence of active exploitation. Triggering requires a crafted WARC file and a vulnerable application to process it. The CVSS vector indicates local access, low complexity, low privileges, and required user interaction; real-world reach depends on each application's archive-ingestion path.

Researcher notes

The documented boundary is a claimed content length above INT64_MAX minus 4. Reported consequences include unpredictable behavior, memory corruption, and denial of service, but the CVSS assigns no integrity impact. Product status is explicit for RHEL 8-10 and OpenShift 4; RHEL 6-7 remains unknown. The bundle does not establish reliable code execution or exploitation in the wild.

Mitigation direction

  • Upgrade libarchive to 3.8.0 or a vendor-provided fixed package.
  • Check Red Hat guidance for supported RHEL and OpenShift remediation packages.
  • Restrict or disable untrusted WARC ingestion until affected components are updated.
  • Apply file-size and format validation before WARC files reach libarchive.

Validation and detection

  • Inventory direct and transitive libarchive versions across hosts, containers, and application images.
  • Identify applications, importers, scanners, or pipelines that process WARC files.
  • Confirm installed packages against current vendor advisories and affected-product status.
  • Verify WARC handlers reject unreasonable content lengths without crashes or memory errors.
  • Retest rebuilt containers and systems to confirm vulnerable library copies are removed.
Prepared
Confidence
high
Sources
6

Public sources used

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.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-5916 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
3.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
5Timeline events
1ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
3.9CVSS 3.1LowCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:L1.32.5redhat

Vulnerability scoring details

Base CVSS 3.1 score

3.9Low
CVSS 3.1 vector shape for CVE-2025-5916Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timelineredhat

    Made public.

  2. Source timelineredhat

    Reported to Red Hat.

  3. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Unknown vendorlibarchivelibarchive, 0unaffected
Red HatRed Hat Enterprise Linux 10libarchiveaffected
Red HatRed Hat Enterprise Linux 6libarchiveunknown
Red HatRed Hat Enterprise Linux 7libarchiveunknown
Red HatRed Hat Enterprise Linux 8libarchiveaffected
Red HatRed Hat Enterprise Linux 9libarchiveaffected
Red HatRed Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9affected
Weakness

CWE details

CWE-190

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.