Skip to main content
VulnerabilityPublished Updated

CVE-2026-74907: getgrav grav · Path Traversal

Affects getgrav gravSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 2.0.15 soon.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.0.15
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 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.0.15.

Affected software

ProductAffectedFixed in
getgravgravAffected
  • <2.0.15
Fixed in
  • 2.0.15
GitHubgetgrav/gravpkg:github/getgrav/gravOther threatsAffected
  • <2.0.15
Fixed in
  • 2.0.15

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

AI-suggested

A fix is available in Grav version 2.0.15. Users should upgrade to version 2.0.15 or later to remediate this vulnerability. Until patched, restricting access to the Grav installation and monitoring for suspicious requests may help reduce risk, but upgrading is the recommended action.

Description

Grav versions before 2.0.15 have a path traversal vulnerability in the static asset server within index.php. The vulnerability arises from improper pathname limitation using string prefix matching rather than proper directory-boundary validation. This allows unauthenticated attackers to access files in sibling directories by exploiting directory names that extend the base path string.

References

Community reviews

Loading reviews…