CVE-2026-72826Grav before 1.0.13 Scope Bypass via createApiKey
Updated under an hour ago ()
Does this affect you?
It affects getgrav grav. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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).
- CVSS
- 8.8 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- CWE-266
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- VulnCheck
- NVD analysis
- Deferred
- Record last updated
- Aug 24, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
getgrav grav getgrav:grav (from the name) | before 1.0.13; 1.0.13 not affected | CNA record |
References
- https://github.com/getgrav/grav/security/advisories/GHSA-95v9-4fcj-96ghvendor-advisory
- https://www.vulncheck.com/advisories/grav-before-scope-bypass-via-createapikeythird-party-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.