CVE-2025-5917: Libarchive: off by one error in build_ustar_entry_name() at archive_write_set_format_pax.c
A vulnerability has been identified in the libarchive library. This flaw involves an 'off-by-one' miscalculation when handling prefixes and suffixes for file names. This can lead to a 1-byte write overflow. While seemingly small, such an overflow can corrupt adjacent memory, leading to unpredictable program behavior, crashes, or in specific circumstances, could be leveraged as a building block for more sophisticated exploitation. This bug affects libarchive versions prior to 3.8.0.
Security readout for executives and security teams
Plain-English summary
CVE-2025-5917 is a low-severity memory safety bug in libarchive before 3.8.0. A one-byte overflow can occur while building archive entry names, potentially causing crashes or unpredictable behavior. The published CVSS impact is limited to availability, with no stated confidentiality or integrity impact.
Executive priority
Handle through normal patch management. Escalation is not warranted from the provided evidence, but affected enterprise Linux and OpenShift fleets should be tracked because libarchive is commonly embedded in system workflows.
Technical view
The flaw is an off-by-one write overflow in build_ustar_entry_name() within archive_write_set_format_pax.c, related to prefix and suffix handling for filenames. It is classified as CWE-787. Red Hat lists RHEL 8, 9, 10 and OpenShift Container Platform 4 RHCOS as affected; RHEL 6 and 7 status is unknown.
Likely exposure
Exposure is most relevant where applications or system tools use libarchive to create archives with local or user-supplied filenames. The bundle identifies libarchive versions before 3.8.0 and specific Red Hat platforms as affected, but does not prove every downstream package state or deployment exposure.
Exploitation context
The CVE is not in KEV, and the provided sources do not report active exploitation. CVSS indicates local access, low privileges, user interaction, and availability-only impact. Treat it as a hardening and stability issue unless vendor guidance changes.
Researcher notes
The bundle supports a bounded availability concern from a one-byte write overflow, not a demonstrated code execution path. Avoid assuming exploitability beyond the CVSS vector and vendor text. Downstream fixed package details are not included here.
Mitigation direction
Inventory libarchive package versions across affected Linux and container hosts.
Upgrade libarchive to 3.8.0 or a vendor-fixed downstream package when available.
Track Red Hat advisories for RHEL and OpenShift Container Platform remediation status.
Prioritize systems processing untrusted archive names or user-controlled filesystem paths.
Validation and detection
Check installed libarchive versions against the vendor advisory and upstream 3.8.0 release.
Confirm whether RHEL or RHCOS images inherit an affected package build.
Review applications that create archives from user-controlled filenames.
Monitor vendor errata for fixed package versions and deployment instructions.
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-787: 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-787 · source CWE mapping
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.