CVE-2025-64031 — libarchive 3.8.x before 3.8.2 has a strcpy heap-based buffer overflow in the gzip writer via the...
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.)
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
- CISA SSVC: exploitation "poc"+5
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Libarchive Libarchive).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Exploitation requires user interaction: tighten email/web filtering and warn affected users.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Libarchive | Libarchive | ≥ 3.8.0 and < 3.8.2 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 2.5 | CVSS 3.1 | Low | 1.0 | 1.4 | cve@mitre.org via NIST National Vulnerability Database |
| 2.5 | CVSS 3.1 | Low | — | — | GitHub, Inc. via GitHub Security Advisories |
| 2.5 | CVSS 3.1 | Low | — | — | mitre via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L (score shown at the top: cve@mitre.org) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 14, 2026 → Oct 15, 2026 · 2 reading(s) · max 0.18%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · libarchive/libarchive
- SSVC assessment updated
- Record published
- CVSS changed · 2.5
- Source status changed · → Awaiting Analysis
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
7 on the record
- gist.github.com/ttuurrnn/1365a4a9b1c3d5826a3a9bbe111f26b8
- nvd.nist.gov/vuln/detail/CVE-2025-64031
- github.com/libarchive/libarchive/pull/2734/commits
- github.com/libarchive/libarchive/blob/master/libarchive/archive_write_add_filter
- github.com/advisories/GHSA-pqgv-phc2-5p8r
- github.com/libarchive/libarchive/pull/2734
- github.com/libarchive/libarchive/pull/2734/files
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-5745 Libarchive: a null pointer dereference vulnerability exists in the acl parser of libarchive Apr 7, 2026
- High CVE-2026-5121 Libarchive: libarchive: arbitrary code execution via integer overflow in iso9660 image processing Mar 30, 2026
- High CVE-2026-4424 Libarchive: libarchive: information disclosure via heap out-of-bounds read in rar archive processing Mar 19, 2026
- Medium CVE-2026-4426 Libarchive: libarchive: denial of service via malformed iso file processing Mar 19, 2026
- Medium CVE-2025-60753 Uncontrolled Resource Consumption in Libarchive Nov 5, 2025
- High CVE-2025-5914 Libarchive: double free at archive_read_format_rar_seek_data() in archive_read_support_format_rar.c Jun 9, 2025
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-64031 is "libarchive 3.8.x before 3.8.2 has a strcpy heap-based buffer overflow in the gzip writer via the...", rated Low. It affects Libarchive (Libarchive); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 2.5 describes technical severity. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.