Vulnerability in getgrav/grav (CVE-2026-61449)
Summary
Vulnerability in getgrav/grav (CVE-2026-61449). Risk of unauthorized operations or information disclosure. Exploitable via system.gpm.archive.max_uncompressed_size. Mitigation: upgrade to 2.0.2 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-61449 has been found in getgrav/grav.
Attackers can target a specific entry point like system.gpm.archive.max_uncompressed_size over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade getgrav/grav to 2.0.2 or later.
If unsure, ask your IT team or search "getgrav/grav CVE-2026-61449" on the vendor's site.
CVE-2026-61449 (getgrav/grav) — CWE-409 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: system.gpm.archive.max_uncompressed_size / extractTo / max_files / max_depth
Patched: 2.0.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-409) exists in getgrav/grav. Attackers reach the vulnerable code path via system.gpm.archive.max_uncompressed_size without authentication.
Check the vendor advisory for the affected versions of getgrav/grav. Attack surface: system.gpm.archive.max_uncompressed_size / extractTo / max_files / max_depth.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to 2.0.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'getgrav/grav' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'getgrav/grav' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
getgrav/gravを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade getgrav/grav to 2.0.2ステージング環境で 2.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory vulncheck.com
- advisory github.com
- web github.com
- web nvd.nist.gov
- web github.com