Skip to main content
CVE-2026-130744VulnerabilityPublished

Grav from 2.0.0 before 2.2.18 contains a remote code execution vulnerability that allows page editors to escape the

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-130744· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 2.2.18 soon.

Data as of 18 Nov 2026, 13:52 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.7
CNA (VulnCheck)CVSS 3.18.8
Patch
Available – fixed in 2.2.18
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 and getgrav/grav to 2.2.18.

Affected software

ProductAffectedFixed in
getgravgravAffected
  • >=2.0.0 <2.2.18
Fixed in
  • 2.2.18
GitHubgetgrav/gravpkg:github/getgrav/gravOther threatsAffected
  • >=2.0.0 <2.2.18
Fixed in
  • 2.2.18

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Grav CMS to version 2.2.18 or later, where this vulnerability is fixed. Since the vulnerability is fixed in 2.2.18, applying this official patch is the recommended remediation. No information about alternative mitigations or temporary workarounds is provided.

Description

A remote code execution vulnerability exists in Grav CMS versions from 2.0.0 up to but not including 2.2.18. This flaw allows page editors to bypass the Twig sandbox by sending requests with a specific Host header, enabling attackers to write configuration YAML files that register an unsandboxed Twig namespace and execute shell commands as the web server user.

References

Community reviews

Loading reviews…