CVE
Grav denial of service via unbounded Host-keyed cache growth
- Exploited
- No known exploitation
- Fix
- Fixed in 2.2.18
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
Summary
Grav from 2.0.0 before 2.2.18 contains a resource exhaustion vulnerability that allows unauthenticated attackers to fill the disk by varying the HTTP Host header. Attackers can send requests with distinct Host values to create per-host compiled configuration, blueprint, language and page index caches, causing session, upload and logging failures.
Who should check
Teams running Grav 2.x from 2.0.0 through 2.2.17 behind nginx with the shipped default server or an Apache default virtual host, without a strict server_name or ServerName
Not fixed by: The fix does not bound every per-host rendered cache entry.
“Grav 2.x from 2.0.0 up to and including 2.2.17”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: 2.2.18.
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-130749 (Grav 2.0.0 before 2.2.18 Unbounded Cache Growth via Host Header), 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-130749 (entry last updated 2026-11-18):
Affected:
- getgrav grav: from 2.0.0, fixed in 2.2.18
Fixed versions: 2.2.18.
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 (source: https://github.com/getgrav/grav/security/advisories/GHSA-j9j4-qq25-7m54)
- A front end routes unknown Host values to Grav, as the shipped nginx.conf default server and a default Apache virtual host do (source: https://github.com/getgrav/grav/security/advisories/GHSA-j9j4-qq25-7m54)
- No strict server_name or ServerName is configured (source: https://github.com/getgrav/grav/security/advisories/GHSA-j9j4-qq25-7m54)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130749 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130749 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-j9j4-qq25-7m54
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-130749
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-130749"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- getgrav grav
From 2.0.0 · fixed in 2.2.18
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · getgrav/grav · Advisory GHSA-j9j4-qq25-7m54 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130749 |
| Record | NVD · CVE-2026-130749 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130749
Is CVE-2026-130749 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 unauthenticated attacker can fill the server disk with redundant cache files. After that, sessions, cache writes, uploads and logging fail until the cache is cleared.Source: github.com
Which versions are affected by CVE-2026-130749?
grav: from 2.0.0 before 2.2.18.Source: cve.now feed data
Am I affected, and how do I check?
Grav 2.x from 2.0.0 up to and including 2.2.17 is affected. Reachability requires a front end that routes unknown Host values to Grav, as the shipped nginx.conf default server and a default Apache virtual host do. To check a setup, look at the installed Grav version and whether nginx server_name or Apache ServerName is set strictly.Source: github.com
How do I fix CVE-2026-130749?
Upgrade Grav to 2.2.18, the version where the range ends. A strict server_name or ServerName also mitigates the issue.Source: github.com