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

> Attackers with minimal API scopes can create unscoped super keys, escalating privileges and potentially achieving remote code execution.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Aug 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-6959-h8j7-rr7m

## What is CVE-2026-72826?

CVE-2026-72826 is a high-severity vulnerability in getgrav grav-plugin-api, published on 14 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

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

Weakness: CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2026-72826?


## How do I fix CVE-2026-72826?

No fix has been published for CVE-2026-72826 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-72826 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72826 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72826 and fix it if it is affected.

What it is: CVE-2026-72826 is a high-severity vulnerability in getgrav grav-plugin-api, published on 14 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72826 exists.

Affected product: getgrav grav-plugin-api. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72826/ (Markdown: https://insights.sbomify.com/CVE-2026-72826/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72826
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72826
- OSV: https://osv.dev/vulnerability/CVE-2026-72826

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72826/
Summaries are generated and may contain mistakes; the official description above is the record.