Grav before 1.0.13 Scope Bypass via createApiKey (CVE-2026-72826) | HOL Guard CVE

Critical · CVSS 9.8CVE-2026-72826

Grav before 1.0.13 Scope Bypass via createApiKey

Answer in brief

CVE-2026-72826 records a Critical severity (CVSS 9.8) vulnerability in Grav before 1.0.13 Scope Bypass via createApiKey. The current sources do not mark it as known exploited. The current feed maps getgrav/grav (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 14, 2026Updated Sep 8, 2026Source checked Sep 29, 2026First seen by HOL Aug 14, 2026Material review Sep 8, 2026

Upstream Advisory

Key facts

Risk: Critical · CVSS 9.8
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps getgrav/grav (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
getgrav/gravgeneric	>=0 <1.0.13	1.0.13

Recommended response

Check inventory. Check lockfiles and deployed manifests for getgrav/grav.
Review the reported fix. Update getgrav/grav to 1.0.13 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 14, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 8, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 14, 2026

Sources and claim methodology

Upstream source description

The getgrav/grav-plugin-api plugin before 1.0.13 fails to validate that the scopes of a newly created API key are a subset of the caller's scopes in createApiKey. The self-target path of requireApiKeyPermission() requires only the baseline api.access scope, and the new key's scopes are read directly from the request body with no subset check. An attacker holding a minimal-scope API key on a super account can submit an empty scopes array to mint an unscoped, full-access super key, bypassing scope restrictions (and enabling further chains such as configuration write to RCE).

Quoted source text, attributed separately from HOL analysis.