# CVE-2026-65895: Grav API Plugin before 1.0.10 Broken Access Control

> Authenticated users can modify security settings to disable rate limiting and alter CORS, facilitating brute-force attacks and credential theft.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/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:** 23 Jul 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-4pqv-2qj5-38fp, GHSA-cvg5-68p3-p7qp

## What is CVE-2026-65895?

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

### Official description

Grav API Plugin versions before 1.0.10 fail to restrict write access to security-critical plugin configuration scopes, allowing authenticated users with api.config.write privilege to modify rate limiting and CORS settings. Attackers can disable rate limiting site-wide to enable credential brute-forcing attacks and reconfigure CORS policies to include attacker-controlled origins with credentials enabled.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-65895 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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