Skip to main content
VulnerabilityPublished

CVE-2026-130743: getgrav grav · External Control of File Name or Path

Affects getgrav gravSource CVE Database V5

0
Compare

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

Data as of 18 Nov 2026, 12:04 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 getgrav grav to 2.2.18.

Affected software

ProductAffectedFixed in
getgravgravAffected
  • >=2.0.0 <2.2.18
Fixed in
  • 2.2.18

AI-suggested

Upgrade Grav to version 2.2.18 or later, where this vulnerability is fixed. No other mitigations are specified or required.

Description

Grav versions from 2.0.0 up to but not including 2.2.18 contain a vulnerability in the blueprint trust mechanism that allows publisher accounts to read sensitive secrets and execute arbitrary PHP code. This is achieved by manipulating blueprint files via the import@ directive, specially named YAML media, or form.flash_folder. The vulnerability was fixed in version 2.2.18.

References

Community reviews

Loading reviews…