CVE-2026-130737: Grav 2.0.0 before 2.2.18 Privilege Escalation via YAML Merge Key
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Gravto a version that resolves this vulnerability.Fixed in 2.2.18
Event History
Frequently Asked Questions
Who can exploit this issue?
An attacker must already have either the admin.users.create permission or the api.users.write permission. Those permissions allow submission of crafted user access data containing a YAML merge key.
Can an attacker use this to obtain full administrative control?
Yes. A user manager can nest access maps under a '<<' YAML merge key to bypass super-grant filtering and assign themselves super-admin rights, resulting in full site control.
Which versions are affected?
Grav versions from 2.0.0 up to, but not including, 2.2.18 are affected.
How might attempted exploitation appear in logs or requests?
Review user creation and update activity, especially PATCH requests to /api/v1/users/<self>, for submitted YAML data containing a '<<' key or nested access maps. Also investigate accounts that unexpectedly gained super-admin rights.