CVE-2026-61449: Grav before 2.0.2 Decompression Bomb via Forged ZIP Size

Published Jul 15, 2026
·
Updated

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.maxuncompressedsize 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.

Affected Software

1 affected component
Grav Grav<2.0.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Grav to a version that resolves this vulnerability.

    Fixed in 2.0.2
  2. Configuration

    Use the decompression-bomb size-cap introduced in v2.0.1: sum the uncompressed sizes declared in each entry's ZIP central-directory header (ZipArchive::statIndex()['size']) and reject archives exceeding system.gpm.archive.max_uncompressed_size before extraction.

    Grav GPM system.gpm.archive.max_uncompressed_size = (enforce/keep the size bound introduced in 2.0.1)
  3. Compensating control

    Ensure archives are supplied only by a trusted package source or admin upload (admin/operator trust) since the decompression-bomb size-cap bypass exists in Grav 2.0.1 (ZipArchiver and GPM\Installer).

Event History

Jul 15, 2026
CVE Published
via MITRE·11:25 AM
Data Sourced
via MITRE·11:25 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·12:18 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-61449?

The severity of CVE-2026-61449 is rated high with a score of 7.1.

2

What is CVE-2026-61449?

CVE-2026-61449 refers to a decompression-bomb size-cap bypass vulnerability in Grav versions prior to 2.0.2.

3

How do I fix CVE-2026-61449?

To fix CVE-2026-61449, upgrade your Grav installation to version 2.0.2 or later.

4

What are the potential impacts of CVE-2026-61449?

The potential impact of CVE-2026-61449 includes denial of service due to system resource exhaustion.

5

Which versions of Grav are affected by CVE-2026-61449?

CVE-2026-61449 affects Grav versions 2.0.1 and earlier.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203