CVE-2026-61449
Grav 2.0.1 contains a decompression-bomb size-cap bypass in …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/getgrav/grav/security/advisories/GHSA-8h9x-89f2-m7x3
- www.vulncheck.com/advisories/grav-before-decompression-bomb-via-forged-zip-size
- nvd.nist.gov/vuln/detail/CVE-2026-61449
- nvd.nist.gov/vuln/detail/CVE-2026-61841
- github.com/advisories/GHSA-8h9x-89f2-m7x3
- nvd.nist.gov/vuln/detail/CVE-2026-61449
- cve.org/CVERecord?id=CVE-2026-61449
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.