Grav 2.0.1 contains a decompression-bomb size-cap bypass in ZipArchiver and GPM\Installer. The size bound introduced in 2.0.1 sums the uncompressed size declared in each entry's ZIP central-directory header (ZipArchive::statIndex()['size']) and rejects archives exceeding system.gpm.archive.max_uncompressed_size before extraction. Because this declared size is attacker-forgeable and is not cross-checked against the actual inflated stream, a crafted archive declaring tiny per-entry sizes passes the cap while extractTo() writes the real, much larger content, filling disk or exhausting inodes. The archive must be supplied by a package source or admin upload (admin/operator trust). Fixed in 2.0.2. This is an incomplete fix for GHSA-928x-9mpw-8h56.
CVE-2026-61449
This medium-severity CVE scores 6.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- 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
- 6.5
- EG Score
- 6.5(low)
- EPSS
- —
- KEV
- Not listed
Published
July 15, 2026
Last Modified
July 15, 2026
Advisory Details (2)
Auto-updated Jul 15, 2026Grav before 2.0.2 Decompression Bomb via Forged ZIP Size | Advisories | VulnCheck
https://www.vulncheck.com/advisories/grav-before-decompression-bomb-via-forged-zip-sizeDecompression-bomb size cap bypassed by forged ZIP size in ZipArchiver/Installer · Advisory · getgrav/grav · GitHub
https://github.com/getgrav/grav/security/advisories/GHSA-8h9x-89f2-m7x3Vendor Advisories for CVE-2026-61449(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 2× in last 7d / 2× 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-15 11:54 UTCEG score recompute
- 2026-07-15 11:54 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-61449?
When was CVE-2026-61449 disclosed?
What is the CVSS score of CVE-2026-61449?
How do I remediate CVE-2026-61449?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-61449
Is Your Infrastructure Affected by CVE-2026-61449?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.