CVE-2026-61449

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-15. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
Elevated
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
6.5
EG Score
6.5(high)
EPSS
16.1%
KEV
Not listed

Published

July 15, 2026

Last Modified

July 15, 2026

Advisory Details (2)

Auto-updated Jul 15, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

Grav before 2.0.2 Decompression Bomb via Forged ZIP Size | Advisories | VulnCheck

https://www.vulncheck.com/advisories/grav-before-decompression-bomb-via-forged-zip-size
github Patch Available🟡 PoC Available

Decompression-bomb size cap bypassed by forged ZIP size in ZipArchiver/Installer · Advisory · getgrav/grav · GitHub

https://github.com/getgrav/grav/security/advisories/GHSA-8h9x-89f2-m7x3

Vendor Advisories for CVE-2026-61449(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 12× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:25 UTCEPSS rescore
  4. 2026-07-21 15:25 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 02:29 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-16 17:03 UTCEPSS rescore
  10. 2026-07-16 12:19 UTCGHSA enrichment
  11. 2026-07-15 11:54 UTCEG score recompute
  12. 2026-07-15 11:54 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-61449?
CVE-2026-61449 is a medium vulnerability published on July 15, 2026. 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…
When was CVE-2026-61449 disclosed?
CVE-2026-61449 was first published in the National Vulnerability Database on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61449 actively exploited?
CVE-2026-61449 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 16.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-61449?
CVE-2026-61449 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-61449?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61449, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-61449

Explore →

Is Your Infrastructure Affected by CVE-2026-61449?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs