Grav before 1.7.53.7 and 2.x before 2.2.18 serves page media files, and rendered pages when lazy sessions are enabled
Source GCVE Database
Not known to be exploited · CVSS 7.7 High : upgrade to 2.2.18 soon.
Data as of 18 Nov 2026, 13:52 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 7.7 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 7.5 |
- Patch
- Available – fixed in 2.2.18, 1.7.53.7
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/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 grav to 2.2.18; grav to 1.7.53.7; getgrav/grav to 2.2.18 or 1.7.53.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| getgravgrav | Affected
| Fixed in
|
| getgravgrav | Affected
| Fixed in
|
GitHubgetgrav/gravpkg:github/getgrav/gravOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Grav CMS versions 1.7.53.7 and 2.2.18 and later. Users should upgrade to these or newer versions to remediate the vulnerability. Until patched, disabling lazy sessions or configuring caches to not store Set-Cookie responses can mitigate the risk. Verify vendor advisories for detailed remediation steps.
Description
Grav CMS versions before 1.7.53.7 and 2.x before 2.2.18 have a vulnerability where page media files and rendered pages served with lazy sessions enabled include the visitor's session cookie and a shared-cacheable Cache-Control header. This allows shared caches like Apache mod_cache to store responses containing Set-Cookie headers. An attacker can exploit this by tricking a logged-in user to access a specially crafted media URL, then retrieve the cached response to obtain the user's session cookie and hijack their session.