CVE
Grav session hijacking via cacheable media responses
Only Grav 2.0.0 through 2.2.17 and 1.7 through 1.7.53.6 behind a shared cache that stores Set-Cookie responses, such as Apache mod_cache with a plain CacheEnable, are exposed. Fixed in 2.2.18 and 1.7.53.7.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.2.18, 1.7.53.7
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Grav 2.x from 2.0.0 up to and including 2.2.17, or Grav 1.7 up to and including 1.7.53.6. A shared HTTP cache that stores responses carrying Set-Cookie is in front of the site, such as Apache mod_cache with a plain CacheEnable. A victim must be signed in through the front-end /login form.
Summary
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, with the visitor's session cookie and a shared-cacheable Cache-Control header. When a shared cache such as Apache mod_cache stores Set-Cookie responses, an attacker can lure a user signed in through the front-end login to open a media URL with a unique query string, then request that URL to receive the cached session cookie and take over the session.
Who should check
Teams running Grav CMS 2.x or 1.7 behind a shared cache such as Apache mod_cache that stores Set-Cookie responses.
“Only sites that run a shared cache that stores Set-Cookie responses are exposed, for example Apache mod_cache with a plain CacheEnable”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.7/10CVSS 7.7
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
Grav 2.x from 2.0.0 up to and including 2.2.17, or Grav 1.7 up to and including 1.7.53.6. A shared HTTP cache that stores responses carrying Set-Cookie is in front of the site, such as Apache mod_cache with a plain CacheEnable. A victim must be signed in through the front-end /login form.Upgrade to a fixed version: 2.2.18, 1.7.53.7.
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-130746 (Grav before 2.2.18 Session Hijacking via Shared-Cacheable Media Responses), 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-130746 (entry last updated 2026-11-18):
Affected:
- getgrav grav: from 2.0.0, fixed in 2.2.18
- getgrav grav: fixed in 1.7.53.7
Fixed versions: 2.2.18, 1.7.53.7.
Conditions (all must be true for the bug to be hit):
- Grav 2.x from 2.0.0 up to and including 2.2.17, or Grav 1.7 up to and including 1.7.53.6. (source: https://github.com/getgrav/grav/security/advisories/GHSA-rxcr-hmmj-6j2c)
- A shared HTTP cache that stores responses carrying Set-Cookie is in front of the site, such as Apache mod_cache with a plain CacheEnable. (source: https://github.com/getgrav/grav/security/advisories/GHSA-rxcr-hmmj-6j2c)
- A victim must be signed in through the front-end /login form. (source: https://github.com/getgrav/grav/security/advisories/GHSA-rxcr-hmmj-6j2c)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-130746 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130746 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-rxcr-hmmj-6j2c
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-130746
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-130746"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- getgrav grav
From 2.0.0 · fixed in 2.2.18
- getgrav grav
fixed in 1.7.53.7
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · getgrav/grav · Advisory GHSA-rxcr-hmmj-6j2c |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130746 |
| Record | NVD · CVE-2026-130746 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130746
Is CVE-2026-130746 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?
An anonymous visitor can take over a signed-in session and act with that user's privileges for as long as the session lives, which is 30 minutes by default.Source: github.com
Which versions are affected by CVE-2026-130746?
grav: from 2.0.0 before 2.2.18. grav: before 1.7.53.7.Source: cve.now feed data
Am I affected, and how do I check?
Grav 2.0.0 through 2.2.17 and Grav 1.7 through 1.7.53.6 are in the affected range, but only on sites with a shared cache that stores responses carrying Set-Cookie, such as Apache mod_cache with a plain CacheEnable, and where a victim signs in through the front-end /login form. Check the installed Grav version and whether a shared cache sits in front of the site.Source: github.com
How do I fix CVE-2026-130746?
Upgrade Grav 2.x to 2.2.18 or later, or Grav 1.7 to 1.7.53.7 or later.Source: github.com