CVE-2026-130737: getgrav grav · Improper Neutralization of Special Elements
Affects getgrav gravSource CVE Database V5
Not known to be exploited · CVSS 8.6 High : upgrade to 2.2.18 soon.
Data as of 18 Nov 2026, 12:05 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 8.6 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 7.2 |
- Patch
- Available – fixed in 2.2.18
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade getgrav grav to 2.2.18.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| getgravgrav | Affected
| Fixed in
|
AI-suggested
Upgrade Grav to version 2.2.18 or later, where this vulnerability is fixed. No other mitigations are specified. Applying the official fix fully addresses the issue.
Description
Grav versions from 2.0.0 up to but not including 2.2.18 contain a privilege escalation vulnerability. This flaw allows user managers with certain permissions to escalate their privileges to super-admin by exploiting improper neutralization of special YAML elements. Specifically, attackers with admin.users.create or api.users.write permissions can submit YAML payloads containing merge keys ('<<') via API requests to bypass super-grant filtering and gain full site control. The vulnerability is fixed in version 2.2.18.