Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-42608: Unauthenticated Path Traversal in Grav CMS FormFlash

Published May 11, 2026 · Updated 7 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days4 mentions · peak 3 in a dayToday
CVSS8.8High · v4
EPSS0.60%49th percentile
CISA KEVNoNot listed
In the wildReported7 exploitation records in Mallory
Vendor
Getgrav
IdentifiersCVE-2026-42608CWE-22 · Improper Limitation of a Pathname…

CVE-2026-42608 is an unauthenticated path traversal vulnerability in the FormFlash component of Grav CMS core. Insufficient validation of form-related identifiers before their use in filesystem paths allows remote attackers to escape the intended temporary storage directory. Manipulating the session_id value supplied through the __form-flash-id POST parameter permits directory creation and writing attacker-controlled YAML metadata outside the intended location. Exploitation details also identify unique_form_id as a traversal input in core form-upload handling. The vulnerability can alter application behavior, compromise data integrity, and disrupt service. Fixes are available in Grav 2.0.0-beta.2 and in the legacy 1.7 branch starting with 1.7.53.4. Exposure depends on Grav core rather than the Form plugin version.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation permits unauthorized filesystem modifications within the Grav process's write permissions, including directory creation and attacker-controlled metadata writes outside intended temporary storage. These modifications can change application behavior, enable website defacement, damage data integrity, and disrupt service. Exploitation was confirmed in the compromise of Clop's leak site. Associated claims of source-code, log, and private-key theft were disputed and do not establish an arbitrary-read or code-execution primitive from this vulnerability alone.

Mitigation

If you can’t patch tonight, do this now.

No vendor-supported workaround is identified. Pending upgrade, restrict access to vulnerable form-processing endpoints or temporarily disable the affected functionality. Apply least-privilege filesystem permissions to limit where the Grav process can create directories and write files. These measures reduce exposure or impact but do not replace the core update.

Remediation

Patch, then assume compromise.

Upgrade Grav 1.7 installations to version 1.7.53.4 or a later fixed release. For Grav 2.x, use version 2.0.0-beta.2 or later. Updating only the Form plugin does not remediate the vulnerable core code. The fix introduces sanitizeId() validation that restricts identifiers to the allowlist pattern [A-Za-z0-9,_-]{1,64}, preventing traversal characters from being used as filesystem path components.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GetgravGravapplication
FAQ

Frequently asked questions

Is CVE-2026-42608 exploited in the wild?
Yes. As of Nov 11, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2026-42608?
Yes. As of Nov 11, 2026, Mallory has reports of a public exploit for CVE-2026-42608.
Is there a patch for CVE-2026-42608?
Upgrade Grav 1.7 installations to version 1.7.53.4 or a later fixed release. For Grav 2.x, use version 2.0.0-beta.2 or later.
What products are affected by CVE-2026-42608?
Getgrav Grav.
How severe is CVE-2026-42608?
CVE-2026-42608 has a CVSS v4 score of 8.8 (High) and an EPSS score of 0.60% (49th percentile) as of Nov 11, 2026.
Activity feed

Recent activity

11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
nuclei templates pull requestsNews · Nov 11, 2026Add [KEV] CVE-2026-42608.yaml - Grav CMS < 1.7.53.4 - Unauthenticated Path Traversal via FormFlash by Akokonunes · Pull Request #17752 · projectdiscovery/nuclei-templatesAn unauthenticated path traversal vulnerability involving FormFlash in Grav CMS versions before 1.7.53.4. The reference documents adding a vulnerability YAML file and a KEV tag, indicating known exploitation, but provides no exploitation details.Read more ↗malware newsNews · Oct 27, 2026September 2026: FBI Breach, Clop Hijack & IDScan Leak - Malware News - Malware Analysis, News and IndicatorsA path traversal vulnerability in Grav CMS exploited by ShinyHunters to compromise and deface Clop's leak site. Grav 2.0 included a fix in April 2026; the affected 1.7 branch received a patch in version 1.7.53.4 on September 24.Read more ↗socradar blogNews · Oct 27, 2026September 2026: FBI Breach, Clop Hijack & IDScan LeakA Grav CMS path traversal vulnerability exploited by ShinyHunters to compromise and deface Clop's leak site. Grav 2.0 fixed it in April 2026; the 1.7 branch received a patch in version 1.7.53.4 on September 24.Read more ↗scworldNews · Sep 28, 2026Clop ransomware gang moves to new server after Grav CMS vulnerability exploited | brief | SC MediaAn unauthenticated path traversal vulnerability in Grav CMS core. It was exploited to compromise Clop's Grav CMS leak-site server and steal server content, logs, source code, and private keys. Grav 2.0 already contained the fix; Grav 1.7.53.4 backports the remediation for the affected 1.7 branch.Read more ↗
+2 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence4Every report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.