CVE-2026-130745: getgrav grav · Incorrect Authorization
Affects getgrav gravSource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 2.2.18 soon.
Data as of 18 Nov 2026, 12:03 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 8.2 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 5.9 |
- Patch
- Available – fixed in 2.2.18
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/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 mitigation is required as the patch addresses the root cause.
Description
Grav versions from 2.0.0 up to but not including 2.2.18 have an access control bypass vulnerability. This flaw allows anonymous users to read protected pages due to shared page cache keys between admin and site scopes. The issue arises when the API plugin rebuilds the page index without enforcing frontmatter.yaml access rules, temporarily exposing members-only content until the cache is refreshed. The vulnerability is rated high severity with a CVSS 4.0 score of 8.2. A fix is available in version 2.2.18.