Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-61449 medium CVSS 6.5

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.

Summary

The decompression-bomb bound added in 2.0.1 (commit 1c1003c) sums ZipArchive::statIndex($i)['size'] and rejects an archive whose declared uncompressed total exceeds system.gpm.archive.max_uncompressed_size (default 1 GiB) before extracting (ZipArchiver.php:77-86; same logic in GPM\Installer::unZip at Installer.php:228-238). statIndex()['size'] is the uncompressed size declared in the ZIP central directory, which is attacker-forgeable and is not checked against the actual inflated stream. An archive declaring 1 byte per entry passes the cap while extractTo() writes the real (large) content. The entry-count and nesting-depth caps count real structure and still hold; only the size dimension is defeated, so the disk-fill / inode-exhaustion case the bound targets is not prevented. Incomplete fix for GHSA-928x-9mpw-8h56.

Details

extract()/unZip() validate every entry up front, then call Folder::create + extractTo. The size check is:

$totalSize += (int) $stat['size'];          // declared central-directory size
if ($maxSize > 0 && $totalSize > $maxSize) { ... reject ... }

$stat['size'] is read from the central directory, which the archive author writes. libzip does not cross-check declared-vs-actual size during extractTo, so a forged-small value passes the gate and the real stream inflates to disk. The max_files (entry count) and max_depth (entry-name segments) checks are not forgeable this way.

PoC

Build a 10 KiB d…

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.

❓ What is the problem

A vulnerability (CWE-409) exists in getgrav/grav. Attackers reach the vulnerable code path via system.gpm.archive.max_uncompressed_size without authentication.

📍 Affected scope

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

Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.0.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

  1. 1
    Identify exposure identify 
    grep -r 'getgrav/grav' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で getgrav/grav を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade getgrav/grav to 2.0.2

    ステージング環境で 2.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

composer getgrav/grav
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details