# CVE-2026-75835: Grav API Plugin before 1.0.14 Missing Authorization

> An attacker with a scoped API key can bypass scope restrictions to access unauthorized UI metadata and item definitions, leading to information disclosure.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 18 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-c746-wcwc-p482

## What is CVE-2026-75835?

CVE-2026-75835 is a critical missing authorization vulnerability in getgrav grav, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Grav API plugin (getgrav/grav-plugin-api) before 1.0.14 contains a missing authorization vulnerability in userPassesAuthorize() (AbstractApiController.php). The function fails to consult the calling request's API key scopes, relying instead on the account's raw super-admin flag and ACL grants. As a result, an authenticated attacker holding a scoped API key minted on a privileged account can bypass their declared scope restrictions to access authorize-gated UI metadata and item definitions (sidebar/menubar/widget items and users-list columns/row-actions/filter-tabs) that their key scope should deny, resulting in information disclosure.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-75835 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75835 is a critical missing authorization vulnerability in getgrav grav, published on 18 Aug 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-75835 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-75835/ (Markdown: https://insights.sbomify.com/CVE-2026-75835/index.md)
```

## Sources

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

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