Quick answers
- Is CVE-2026-62237 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-62237 being exploited in the wild.
- How severe is CVE-2026-62237?
- Medium severity, with a CVSS score of 6.5, published 17 July 2026.
- Which products and versions are affected?
- Grav before 2.0.4; getgrav/grav (Packagist) ECOSYSTEM:introduced=0,fixed=2.0.4.
- Is there a fix for CVE-2026-62237?
- Yes. getgrav/grav (Packagist): upgrade to 2.0.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-62237 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-62237?
- Check whether you run Grav or getgrav/grav (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- getgrav/grav (Packagist): upgrade to 2.0.4 or later
composer require getgrav/grav:^2.0.4
Technical details
A Regular Expression Denial of Service (ReDoS) vulnerability exists in Grav's Twig content sandbox due to the allowlisting of the 'regex_replace' filter and function. The underlying implementation in GravExtension.php passes user-supplied patterns directly to PHP's preg_replace() without complexity validation. If 'security.twig_content.process_enabled' is set to true, an authenticated attacker with page-editing privileges can embed a catastrophic backtracking PCRE pattern in page content. This results in exponential time complexity during processing, exhausting CPU resources and causing a denial of service (DoS) for the web server process. The issue is fixed in version 2.0.4.
Affected products
- getgrav Grav before 2.0.4
Identifiers
- CVE-2026-62237
- GHSA-37f3-6p89-6qr9
Timeline
- 2026-06-29: advisory: Initial GitHub security advisory published
- 2026-07-17: disclosed: NVD publication date