CVE-2025-64031

libarchive: libarchive: Denial of Service via heap-based buffer overflow in gzip writer

Published Sep 14, 2026 CVSS 3.1 · 2.5 Low EPSS < 1% KEV · Not listed
Description
libarchive 3.8.x before 3.8.2 has a strcpy heap-based buffer overflow in the gzip writer via the original-filename field to archive_compressor_gzip_open in archive_write_add_filter_gzip.c, aka GHSA-92wx-p669-8gr9. This relates to bsdtar. Exploitation envisions a marginally plausible scenario in which original-filename is obtained from an untrusted party. (original-filename is not derived from the input data.)

Analysis

AI-generated

Technical impact

A strcpy heap-based buffer overflow exists in libarchive’s gzip writer, triggered by the original‑filename field used in archive_compressor_gzip_open. The overflow can corrupt the heap, potentially leading to a memory corruption. The flaw exists.x before 3.8.2 and directly relates to bsdtar. The vulnerability is confined to processes that load the affected library and invoke the gzip compression path, so impact is local but can is identified as CWE-120 and CWE-122.

Affected Systems

The libc archive component, libarchive, version 3.8.x prior to 3.8.2 is affected. Users of this library, including applications that wrap or use libarchive for gzip archive creation (for example bsdtar), should verify the version and consider upgrading.

Risk and Exploitability

The vulnerability carries a CVSS score of 2.5, indicating low overall severity, and has an EPSS score of < 1%, indicating a marginally plausible exploitation scenario. It is not listed in CISA’s KEV catalog. The likely attack vector involves an attacker supplying a crafted original‑filename field to a process that uses libarchive’s gzip writer. Because the original‑filename is not derived from other input data, the scenario requires the attacker to control the filename supplied by the application or the environment. Low CVSS and limited exploitation probability mitigate immediate risk; nevertheless, the presence of a heap‑based overwrite warrants remediation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade libarchive to version 3.8.2 or later, which contains a fixed strcpy guard in the gzip writer.
  • If upgrading is not immediately possible, avoid passing untrusted data into the original‑filename field or sanitize the filename string before use to prevent overflow.
  • For critical environments where the library cannot be updated, consider disabling the gzip writer or configuring the application to omit the original‑filename altogether.

Generated by OpenCVE AI on September 15, 2026 at 15:48 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Title Heap Overflow in libarchive Gzip Writer via Original-Filename libarchive: libarchive: Denial of Service via heap-based buffer overflow in gzip writer
Weaknesses CWE-120
References
Metrics threat_severity

None

threat_severity

Moderate

Type Values Removed Values Added
Title Heap Overflow in libarchive Gzip Writer via Original-Filename
Type Values Removed Values Added
Description libarchive 3.8.x before 3.8.2 has a strcpy heap-based buffer overflow in the gzip writer via the original-filename field to archive_compressor_gzip_open in archive_write_add_filter_gzip.c, aka GHSA-92wx-p669-8gr9. This relates to bsdtar. Exploitation envisions a marginally plausible scenario in which original-filename is obtained from an untrusted party. (original-filename is not derived from the input data.)
First Time appeared Libarchive
Libarchive libarchive
Weaknesses CWE-122
CPEs cpe:2.3:a:libarchive:libarchive:*:*:*:*:*:*:*:*
Vendors & Products Libarchive
Libarchive libarchive
References
Metrics cvssV3_1

{'score': 2.5, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L'}

Weaknesses
  • CWE-120

    Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

  • CWE-122

    Heap-based Buffer Overflow

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
Sep 16, 2026, 2:22 PM
Reserved
Oct 27, 2025, 12:00 AM
Status
Awaiting Analysis
Published
Sep 14, 2026, 1:16 AM
Modified
Oct 14, 2026, 7:10 PM
Severity
Moderate
Public date
Sep 14, 2026, 12:00 AM