Vulnerability Description
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.
CVSS Score
MEDIUM
Related Weaknesses (CWE)
References
- https://github.com/getgrav/grav/security/advisories/GHSA-8h9x-89f2-m7x3
- https://www.vulncheck.com/advisories/grav-before-decompression-bomb-via-forged-z
- https://github.com/getgrav/grav/security/advisories/GHSA-8h9x-89f2-m7x3
FAQ
What is CVE-2026-61449?
CVE-2026-61449 is a vulnerability with a CVSS score of 6.5 (MEDIUM). 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 ...
How severe is CVE-2026-61449?
CVE-2026-61449 has been rated MEDIUM with a CVSS base score of 6.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-61449?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.