# CVE-2026-65007: Grav before 1.0.8 Missing Authorization on API Key Generation

> Any user with admin.login can generate API keys for other accounts, enabling impersonation and privilege escalation in Grav CMS.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 23 Jul 2026
- **Also known as:** GHSA-6m96-62fv-f2wh

## What is CVE-2026-65007?

CVE-2026-65007 is a high-severity missing authorization vulnerability in getgrav grav, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Grav api plugin (grav-plugin-api) before 1.0.8 fails to properly authorize API key generation and revocation: the plugin intercepts the apiKeyGenerate/apiKeyRevoke admin tasks before the account-management ACL runs and authorizes the caller on only the admin.login permission (the baseline permission held by every panel user). This allows any user with admin.login to mint a persistent API key bound to any account, and the forged key inherits the target account's API permissions. On installs where an API-enabled account holds broader permissions, this enables account impersonation and privilege escalation up to account takeover.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-65007 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-65007 is a high-severity missing authorization vulnerability in getgrav grav, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-65007 exists.

Affected product: getgrav grav. 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-65007/ (Markdown: https://insights.sbomify.com/CVE-2026-65007/index.md)
```

## Sources

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

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