adm-zip before 0.5.18 is vulnerable to denial of service via a crafted ZIP file with a manipulated uncompressed size header field. In zipEntry.js line 103, Buffer.alloc(_centralHeader.size) allocates memory based on the declared uncompressed size from the ZIP central directory header without validating it against the actual compressed data size or imposing any upper bound. The size value is read directly from the binary header at entryHeader.js line 266 with no bounds check. An attacker can craft a ~120-byte ZIP file that declares ~4GB uncompressed size, causing a memory allocation amplification ratio of over 33 million to 1. The allocation occurs before CRC validation, so the malicious payload cannot be rejected early. All extraction and read methods are affected: readFile(), readAsText(), extractEntryTo(), extractAllTo(), extractAllToAsync(), test(), and entry.getData(). Any application accepting untrusted ZIP files via adm-zip is vulnerable to immediate process crash.
CVE-2026-39244
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-10. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EPSS
- 34.8%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 10, 2026
Advisory Details (2)
Auto-updated Jul 10, 2026[CVE-2026-39244] Denial of service via unbounded Buffer.alloc from crafted uncompressed-size header · Issue #568 · cthackers/adm-zip · GitHub
https://github.com/cthackers/adm-zip/issues/568GitHub - cthackers/adm-zip: A Javascript implementation of zip for nodejs. Allows user to create or extract zip files both in memory or to/from disk · GitHub
https://github.com/cthackers/adm-zipVendor Advisories for CVE-2026-39244(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 14× in last 7d / 14× 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-07-14 10:10 UTCEG score recompute
- 2026-07-14 10:10 UTCGHSA enrichment
- 2026-07-13 23:07 UTCEG score recompute
- 2026-07-13 23:07 UTCGHSA enrichment
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 12:04 UTCEG score recompute▲ 7.50
- 2026-07-13 12:04 UTCGHSA enrichment
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-10 18:22 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
- 2026-07-10 18:19 UTCNVD update
- 2026-07-10 16:33 UTCEG score recompute
- 2026-07-10 16:32 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-400
Frequently asked(5)
What is CVE-2026-39244?
When was CVE-2026-39244 disclosed?
Is CVE-2026-39244 actively exploited?
What is the CVSS score of CVE-2026-39244?
How do I remediate CVE-2026-39244?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-39244
Is Your Infrastructure Affected by CVE-2026-39244?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.