Is CVE-2026-62230 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-62230 being exploited in the wild.

How severe is CVE-2026-62230?

High severity, with a CVSS score of 7.5, published 17 July 2026.

Which products and versions are affected?

Grav < 2.0.4; getgrav/grav (Packagist) ECOSYSTEM:introduced=0,fixed=2.0.4.

Is there a fix for CVE-2026-62230?

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-62230 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-62230?

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.

CVE-2026-62230: Grav .htaccess security bypass via case variation

Q: Which products and versions are affected?

Grav < 2.0.4; getgrav/grav (Packagist) ECOSYSTEM:introduced=0,fixed=2.0.4.

Q: Is there a fix for CVE-2026-62230?

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.

Q: How is CVE-2026-62230 attacked?

It is attacked over the network, in a web application.

Q: Am I affected by CVE-2026-62230?

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.

CVE-2026-62230 · Severity: high · CVSS 7.5 · Published 2026-07-17

Grav, a popular open-source content management system, contains a security flaw in its default web server configuration. When Grav is hosted on systems that do not distinguish between uppercase and lowercase filenames (such as Windows or macOS), an attacker can bypass security restrictions to download sensitive files. This could lead to the exposure of API keys, database credentials, and website source code, potentially allowing for full site compromise.

Technologies: Grav, getgrav/grav (Packagist). Vendors: Grav, Packagist.

Quick answers

Is CVE-2026-62230 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-62230 being exploited in the wild.
How severe is CVE-2026-62230?: High severity, with a CVSS score of 7.5, published 17 July 2026.
Which products and versions are affected?: Grav < 2.0.4; getgrav/grav (Packagist) ECOSYSTEM:introduced=0,fixed=2.0.4.
Is there a fix for CVE-2026-62230?: 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-62230 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-62230?: 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 vulnerability exists in the default .htaccess and webserver-configs/htaccess.txt files provided with Grav. The RewriteRule directives intended to block access to sensitive directories (system/, vendor/, and user/) and file extensions (.yaml, .php, .json, etc.) lack the [NC] (No Case) flag. On case-insensitive filesystems like NTFS (Windows) or HFS+ (macOS), the underlying OS will serve a file even if the request uses different casing, but the Apache mod_rewrite rules will fail to match and block the request. An unauthenticated remote attacker can exploit this by requesting files like 'config.YAML' or 'index.PHP' to bypass the blocklist and exfiltrate sensitive credentials or source code. The issue is resolved in version 2.0.4 by adding the [NC] flag to the affected rules.

Affected products

getgrav Grav < 2.0.4

Identifiers

CVE-2026-62230
GHSA-vwg3-w8w3-pc79

Timeline

2026-06-29: advisory: Initial GitHub Security Advisory published
2026-07-16: disclosed: CVE published to NVD and VulnCheck advisory released
2026-07-17: patched: Fix confirmed available in version 2.0.4

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.