Vulnerability in getgrav/grav (CVE-2026-76839)
Summary
Vulnerability in getgrav/grav (CVE-2026-76839). Confidential information can be exposed externally. Exploitable via offsetget. Mitigation: upgrade to 2.0.16 or later.
Original description
The description as published by the source.
Grav before 2.0.16 allows sandboxed Twig templates to access sensitive User fields through allow-listed offsetGet() and offsetexists() methods that lack field filtering. Attackers with page-edit permissions can call offsetGet() on User objects to extract hashed passwords and 2FA secrets, enabling offline password cracking and authentication bypass.
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-76839 has been found in getgrav/grav.
Attackers can target a specific entry point like offsetget over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade getgrav/grav to 2.0.16 or later.
If unsure, ask your IT team or search "getgrav/grav CVE-2026-76839" on the vendor's site.
CVE-2026-76839 (getgrav/grav) — CWE-522 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: offsetget / offsetexists / User / hashed_password
Patched: 2.0.16 — 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-522) exists in getgrav/grav. Attackers reach the vulnerable code path via offsetget.
Check the vendor advisory for the affected versions of getgrav/grav. Attack surface: offsetget / offsetexists / User / hashed_password.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 2.0.16.
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.16ステージング環境で 2.0.16 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory vulncheck.com
- advisory nvd.nist.gov
- advisory github.com
- web github.com
- web github.com