CVE
Grav arbitrary file read via Twig sandbox bypass
Only regular pages in Grav 2.0.0 through 2.2.17 are affected, and the attacker needs page edit (publisher) rights. Fixed in Grav 2.2.18.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.2.18
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Grav 2.x from 2.0.0 through 2.2.17 Attacker has page edit (publisher) rights Regular pages, the default page type (Flex pages are not affected)
Summary
Grav from 2.0.0 before 2.2.18 contains a Twig sandbox bypass vulnerability that allows publishers to read any server file by abusing allowlisted array_key_value() and page accessor setters such as filePath(). Attackers can repoint page objects or overwrite the assets collections to render private keys and the API signing secret, then forge a super-admin API token.
Who should check
Teams running Grav 2.x (2.0.0 through 2.2.17) where publishers or page editors can edit page content
Not fixed by: Re-adding path or filepath to allowed_methods reopens the file read.
“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
- Exposure8/25Specific setups only, reachable over the network
- 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 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Grav 2.x from 2.0.0 through 2.2.17 Attacker has page edit (publisher) rights Regular pages, the default page type (Flex pages are not 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-130741 (Grav 2.0.0 before 2.2.18 Arbitrary File Read via Twig Sandbox Bypass), 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-130741 (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 through 2.2.17 (source: https://github.com/getgrav/grav/security/advisories/GHSA-8rhf-56h6-j77w)
- Attacker has page edit (publisher) rights (source: https://github.com/getgrav/grav/security/advisories/GHSA-8rhf-56h6-j77w)
- Regular pages, the default page type (Flex pages are not affected) (source: https://github.com/getgrav/grav/security/advisories/GHSA-8rhf-56h6-j77w)
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-130741 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130741 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-8rhf-56h6-j77w
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-130741
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-130741"}.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-8rhf-56h6-j77w |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130741 |
| Record | NVD · CVE-2026-130741 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130741
Is CVE-2026-130741 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?
A publisher with page edit rights can read any file the PHP user can read, including private keys and the API signing secret. They can then forge a super-admin API token, which gives full control of the site.Source: github.com
Which versions are affected by CVE-2026-130741?
grav: from 2.0.0 before 2.2.18.Source: cve.now feed data
Am I affected, and how do I check?
Grav 2.0.0 through 2.2.17 with regular pages, which is the default page type. Flex pages are not affected. To check, compare the installed Grav version with this range and check which page type the site uses.Source: github.com
How do I fix CVE-2026-130741?
Upgrade Grav to 2.2.18 or later. The facts name no vendor patch IDs for this issue.Source: github.com