# CVE-2026-86195: grav-plugin-api 1.0.0 through 1.0.19 Privilege Escalation via Dot-Keyed Super Flag

> A non-super user can escalate to super-admin by injecting dot-keyed flags into invitations, gaining full site control via JWT.

- **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:** 5 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-rg66-gwrp-wj75

## What is CVE-2026-86195?

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

### Official description

grav-plugin-api versions before 1.0.20 contain a privilege escalation vulnerability in the InvitationsController where the stripSuperFlags() method only removes nested super flags but fails to strip dot-keyed equivalents like api.super. A non-super user manager with api.access and api.users.write permissions can create an invitation with a dot-keyed super flag in the access payload that bypasses the guard and persists to the new account. Attackers can accept the invitation through the public endpoint without real invitee interaction to create a super-admin account and immediately receive a valid JWT for full site control.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-86195 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86195 is a high-severity vulnerability in getgrav grav-plugin-api, published on 5 Sep 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-86195 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-86195/ (Markdown: https://insights.sbomify.com/CVE-2026-86195/index.md)
```

## Sources

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

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