Vulnerability in getgrav/grav (CVE-2026-53653)
Summary
Vulnerability in getgrav/grav (CVE-2026-53653). Risk of unauthorized operations or information disclosure. Exploitable via GET /home/test.png. Mitigation: upgrade to 1.7.53 or later.
Original description
The description as published by the source.
Grav is a file-based Web platform. Prior to 1.7.53 and 2.0.0-rc.8, Grav allows an unauthenticated visitor to exhaust server memory and CPU by requesting image derivatives with oversized dimensions through URL query image actions such as forceResize in Grav::fallbackUrl, which passes request parameters to ImageMedium magic actions without a dimension or pixel ceiling. This issue is fixed in versions 1.7.53 and 2.0.0-rc.8.
Source: NIST National Vulnerability Database 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-53653 has been found in getgrav/grav.
Attackers can target a specific entry point like GET /home/test.png over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade getgrav/grav to 1.7.53 or later.
If unsure, ask your IT team or search "getgrav/grav CVE-2026-53653" on the vendor's site.
CVE-2026-53653 (getgrav/grav) — CWE-770
Attack surface: GET /home/test.png / forceResize / emalloc / memory_limit
Patched: 1.7.53 — 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-770) exists in getgrav/grav. Attackers reach the vulnerable code path via GET /home/test.png.
Check the vendor advisory for the affected versions of getgrav/grav. Attack surface: GET /home/test.png / forceResize / emalloc / memory_limit.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.7.53.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /home/test.png requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /home/test.png' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /home/test.pngへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade getgrav/grav to 1.7.53ステージング環境で 1.7.53 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /home/test.png on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com
- web github.com