Skip to main content
Menu
CVEs

CVE

Grav privilege escalation via YAML merge keys in user API

CVE-2026-130737Published Updated

8.6HighCNA
Exploited
No known exploitation
Fix
Fixed in 2.2.18
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Grav 2.0.0 up to and including 2.2.17 The Grav API plugin is also affected in its super-grant check

Summary

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.

cve.now Index

17Pcve.now Index 17 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.6/10CVSS 8.6
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 24 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Grav 2.0.0 up to and including 2.2.17 The Grav API plugin is also affected in its super-grant check
  • Upgrade to a fixed version: 2.2.18.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130737 (Grav 2.0.0 before 2.2.18 Privilege Escalation via YAML Merge Key), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130737 (entry last updated 2026-11-18):
Affected:
- getgrav grav: from 2.0.0, fixed in 2.2.18
Fixed versions: 2.2.18.
Conditions (all must be true for the bug to be hit):
- Grav 2.0.0 up to and including 2.2.17 (source: https://github.com/getgrav/grav/security/advisories/GHSA-gm9r-xmhp-p55q)
- The Grav API plugin is also affected in its super-grant check (source: https://github.com/getgrav/grav/security/advisories/GHSA-gm9r-xmhp-p55q)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-130737 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130737 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/getgrav/grav/security/advisories/GHSA-gm9r-xmhp-p55q
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130737
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130737"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • getgrav grav

    From 2.0.0 · fixed in 2.2.18

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · getgrav/grav · Advisory GHSA-gm9r-xmhp-p55q
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130737
RecordNVD · CVE-2026-130737

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130737

Is CVE-2026-130737 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A user manager, or any account with the api.users.write permission, can become a super admin through a YAML merge key, which gives full control of the site. The Grav API plugin is also affected in its super-grant check.Source: github.com

Which versions are affected by CVE-2026-130737?

grav: from 2.0.0 before 2.2.18.Source: cve.now feed data

Am I affected, and how do I check?

Grav 2.x from 2.0.0 up to and including 2.2.17 is affected, and the Grav API plugin is affected in its super-grant check. To check a Grav install, look at the version reported by the Grav admin or the installed Grav release.Source: github.com

How do I fix CVE-2026-130737?

No fixed version or vendor patch identifiers are listed in the checked facts, so no specific upgrade target can be confirmed here. The affected range ends before 2.2.18, which is the listed fixed version boundary.Source: github.com

More CVEs