CVE-2026-61449: Improper Handling of Highly Compressed Data (Data Amplification) in getgrav grav
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.
AI Analysis
Technical Summary
CVE-2026-61449 describes a decompression-bomb size-cap bypass vulnerability in Grav 2.0.1's ZipArchiver and GPM\Installer. The software enforces a size limit on uncompressed archives by summing declared sizes from ZIP central-directory headers before extraction. However, these declared sizes are attacker-forgeable and not cross-checked against the actual inflated data stream. Consequently, a crafted archive with small declared sizes can bypass the limit, but during extraction, the real, much larger data is written, potentially filling disk space or exhausting inodes. This attack requires the archive to come from a trusted source or admin upload, limiting exposure. The issue was fixed in Grav 2.0.2, though it is noted as an incomplete fix for a related advisory GHSA-928x-9mpw-8h56.
Potential Impact
Successful exploitation can lead to resource exhaustion on the host system by filling disk space or exhausting inodes, potentially causing denial of service or operational disruption. The vulnerability requires administrative or trusted package upload privileges, so it does not allow remote unauthenticated exploitation. No evidence of active exploitation in the wild is reported.
Mitigation Recommendations
A fix is available in Grav version 2.0.2. Users should upgrade to version 2.0.2 or later to remediate this vulnerability. Since the vulnerability requires trusted package sources or admin uploads, restricting upload permissions and verifying package sources can reduce risk. Patch status is not explicitly confirmed in the vendor advisory, but the description states the issue is fixed in 2.0.2. Check the official Grav advisory for the latest remediation guidance.
CVE-2026-61449: Improper Handling of Highly Compressed Data (Data Amplification) in getgrav grav
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 v4.0
Score 7.1high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-61449 describes a decompression-bomb size-cap bypass vulnerability in Grav 2.0.1's ZipArchiver and GPM\Installer. The software enforces a size limit on uncompressed archives by summing declared sizes from ZIP central-directory headers before extraction. However, these declared sizes are attacker-forgeable and not cross-checked against the actual inflated data stream. Consequently, a crafted archive with small declared sizes can bypass the limit, but during extraction, the real, much larger data is written, potentially filling disk space or exhausting inodes. This attack requires the archive to come from a trusted source or admin upload, limiting exposure. The issue was fixed in Grav 2.0.2, though it is noted as an incomplete fix for a related advisory GHSA-928x-9mpw-8h56.
Potential Impact
Successful exploitation can lead to resource exhaustion on the host system by filling disk space or exhausting inodes, potentially causing denial of service or operational disruption. The vulnerability requires administrative or trusted package upload privileges, so it does not allow remote unauthenticated exploitation. No evidence of active exploitation in the wild is reported.
Mitigation Recommendations
A fix is available in Grav version 2.0.2. Users should upgrade to version 2.0.2 or later to remediate this vulnerability. Since the vulnerability requires trusted package sources or admin uploads, restricting upload permissions and verifying package sources can reduce risk. Patch status is not explicitly confirmed in the vendor advisory, but the description states the issue is fixed in 2.0.2. Check the official Grav advisory for the latest remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-09T14:06:14.016Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a57772068715ace43a93bc3
Added to database: 07/15/2026, 12:03:44 UTC
Last enriched: 07/15/2026, 12:17:42 UTC
Last updated: 07/16/2026, 03:36:29 UTC
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.