Service interruption via forged ZIP size metadata
Published Jul 15, 2026 · Updated Jul 15, 2026
Decompression-bomb bypass in Grav 2.0.1 allows attackers to interrupt service through a crafted ZIP archive supplied for extraction. ZipArchiver and GPM\Installer trust each entry's forgeable central-directory size, so extractTo() can inflate far more data than the pre-extraction cap counted. A package source or administrator must supply the archive, and successful exploitation fills disk space or exhausts inodes.
Summary
What happened
Decompression-bomb bypass in Grav 2.0.1 allows attackers to interrupt service through a crafted ZIP archive supplied for extraction. ZipArchiver and GPM\Installer trust each entry's forgeable central-directory size, so extractTo() can inflate far more data than the pre-extraction cap counted. A package source or administrator must supply the archive, and successful exploitation fills disk space or exhausts inodes.
The record
- CVE
- CVE-2026-61449
- Published
- Jul 15, 2026
- Updated
- Jul 15, 2026
- Vendor
- Grav
- Product
- Grav
- Classifications
- CWE-409, T1499.004
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 15, 2026CVE publishedPublication date reported by the CVE source.
- Jul 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.0.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Forged ZIP size decompression-bomb proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo