# CVE-2025-64031: Memory corruption in libarchive

> Heap-based buffer overflow in libarchive's gzip writer allows attackers to execute arbitrary code or cause denial of service via crafted original-filename fields.

- **Severity:** Low 2.5 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-pqgv-phc2-5p8r

## What is CVE-2025-64031?

CVE-2025-64031 is a low-severity memory corruption vulnerability in libarchive, published on 14 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official 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.)

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2025-64031?


## How do I fix CVE-2025-64031?

Upgrade to a fixed version.

## Is CVE-2025-64031 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64031 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-64031 and fix it if it is affected.

What it is: CVE-2025-64031 is a low-severity memory corruption vulnerability in libarchive, published on 14 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64031 exists.

Affected product: libarchive. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-64031/ (Markdown: https://insights.sbomify.com/CVE-2025-64031/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-64031
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-64031
- OSV: https://osv.dev/vulnerability/CVE-2025-64031

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-64031/
Summaries are generated and may contain mistakes; the official description above is the record.