CVE-2026-72826: Grav before 1.0.13 Scope Bypass via createApiKey

Published Aug 14, 2026
·
Updated

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).

Affected Software

2 affected components
Grav Grav<1.0.13
getgrav/grav-plugin-api<1.0.13

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade getgrav/grav-plugin-api to a version that resolves this vulnerability.

    Fixed in 1.0.13
  2. Configuration

    In createApiKey, validate that the scopes provided in the request body for the newly created API key are a subset of the caller's scopes (i.e., reject requests where newly_created_key_scopes are not contained within caller_scopes).

    getgrav/grav-plugin-api createApiKey scopes validation = caller_scopes must be a superset of newly_created_key_scopes
  3. Compensating control

    Until patched, ensure that minimal-scope API keys used by super accounts cannot mint full-access unscoped keys by enforcing external controls around API key creation (e.g., restrict who/what can call createApiKey and require stronger authorization than only the baseline api.access scope).

Event History

Aug 14, 2026
CVE Published
via MITRE·11:35 AM
Data Sourced
via MITRE·11:35 AM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-72826?

The severity of CVE-2026-72826 is rated as critical with a score of 9.8.

2

How do I fix CVE-2026-72826?

To fix CVE-2026-72826, upgrade to Grav before version 1.0.13 of the getgrav/grav-plugin-api plugin.

3

What are the potential impacts of CVE-2026-72826?

CVE-2026-72826 can lead to unauthorized access to sensitive data by allowing API keys with excessive scopes.

4

Who is affected by CVE-2026-72826?

CVE-2026-72826 affects users of Grav and the getgrav/grav-plugin-api plugin prior to version 1.0.13.

5

When was CVE-2026-72826 published?

CVE-2026-72826 was published on August 14, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203