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.)
CVE-2025-64031
Score 2.5 from GitHub Security Advisory (severity: LOW) published 2026-09-14. a secondary CVSS source baseline 2.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 2.5
- EG Score
- 2.5(high)
- EG Risk
- 27(Track)EG Risk 27/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity25% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 2%
- KEV
- Not listed
Published
September 14, 2026
Last Modified
September 16, 2026
References (6)
- cve@mitrehttps://gist.github.com/ttuurrnn/1365a4a9b1c3d5826a3a9bbe111f26b8
- cve@mitrehttps://github.com/libarchive/libarchive/blob/master/libarchive/archive_write_add_filter_gzip.c
- cve@mitrehttps://github.com/libarchive/libarchive/pull/2734
- cve@mitrehttps://github.com/libarchive/libarchive/pull/2734/commits
- cve@mitrehttps://github.com/libarchive/libarchive/pull/2734/files
- 134c704f-9b21-4f2e-91b3-4a467353bcc0https://gist.github.com/ttuurrnn/1365a4a9b1c3d5826a3a9bbe111f26b8
Vendor Advisories for CVE-2025-64031(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 15× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-20 20:15 UTCEPSS rescore
- 2026-09-19 15:42 UTCEPSS rescore
- 2026-09-19 08:26 UTCEG score recompute
- 2026-09-19 08:26 UTCGHSA enrichment
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-17 19:30 UTCEPSS rescore
- 2026-09-16 15:29 UTCEG score recompute
- 2026-09-16 15:29 UTCGHSA enrichment
- 2026-09-16 14:38 UTCEG score recompute
- 2026-09-16 14:38 UTCGHSA enrichment
- 2026-09-16 14:07 UTCEPSS rescore
- 2026-09-15 03:10 UTCEPSS rescore
- 2026-09-14 01:20 UTCEG score recompute
- 2026-09-14 00:40 UTCEG score recompute
- 2026-09-14 00:39 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-122
Frequently asked(5)
What is CVE-2025-64031?
When was CVE-2025-64031 disclosed?
Is CVE-2025-64031 actively exploited?
What is the CVSS score of CVE-2025-64031?
How do I remediate CVE-2025-64031?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-64031
Is Your Infrastructure Affected by CVE-2025-64031?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.