# CVE-2026-130737: Grav 2.0.0 before 2.2.18 Privilege Escalation via YAML Merge Key


- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-gchh-pq2q-8xrj, GHSA-gm9r-xmhp-p55q

## What is CVE-2026-130737?

CVE-2026-130737 is a high-severity vulnerability in getgrav grav, published on 18 Nov 2026. 

### Official description

Grav from 2.0.0 before 2.2.18 contains a privilege escalation vulnerability that allows user managers to grant super-admin rights by nesting access maps under a YAML merge key. Attackers with admin.users.create or api.users.write can submit '<<' keys, for example via PATCH /api/v1/users/<self>, that bypass super-grant filtering and gain full site control.

Weakness: CWE-138 (Improper Neutralization of Special Elements)

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


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

Upgrade getgrav grav to 2.2.18 or later. The advisory says that version fixes it.

## Is CVE-2026-130737 being exploited?

There is no known exploitation of CVE-2026-130737 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130737 is a high-severity vulnerability in getgrav grav, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130737 in the wild and no public exploit code.

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-130737/ (Markdown: https://insights.sbomify.com/CVE-2026-130737/index.md)
```

## Sources

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

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