CVE-2026-62230: Improper Handling of Case Sensitivity in getgrav grav
Grav versions prior to 2.0.4 include a default .htaccess file with rules intended to block access to sensitive file types such as .yaml, .php, and .json. However, these rules lack the case-insensitive ([NC]) flag, causing extension matching to be case-sensitive. On case-insensitive filesystems like Windows NTFS, macOS HFS+, or Docker volume mounts, an unauthenticated attacker can bypass these restrictions by requesting files with uppercase or mixed-case extensions (e.g., .YAML, .PHP). This allows unauthorized reading of sensitive configuration files that may contain API keys and credentials.
AI Analysis
Technical Summary
The vulnerability CVE-2026-62230 affects Grav versions before 2.0.4. The default .htaccess file shipped with these versions contains rules to block access to sensitive file types but does not use the [NC] flag, making the extension matching case-sensitive. On case-insensitive filesystems, this allows an unauthenticated attacker to bypass access restrictions by requesting files with uppercase or mixed-case extensions, potentially exposing sensitive configuration files containing secrets such as API keys and credentials.
Potential Impact
An unauthenticated attacker can bypass .htaccess restrictions on sensitive file types by exploiting case sensitivity issues on case-insensitive filesystems. This can lead to unauthorized disclosure of sensitive configuration files, including those containing API keys and credentials, potentially compromising the security of the affected system.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider manually updating the .htaccess rules to include the [NC] flag for extension matching to enforce case-insensitive blocking of sensitive file types. Monitoring vendor communications for an official patch or update is recommended.
CVE-2026-62230: Improper Handling of Case Sensitivity in getgrav grav
Description
Grav versions prior to 2.0.4 include a default .htaccess file with rules intended to block access to sensitive file types such as .yaml, .php, and .json. However, these rules lack the case-insensitive ([NC]) flag, causing extension matching to be case-sensitive. On case-insensitive filesystems like Windows NTFS, macOS HFS+, or Docker volume mounts, an unauthenticated attacker can bypass these restrictions by requesting files with uppercase or mixed-case extensions (e.g., .YAML, .PHP). This allows unauthorized reading of sensitive configuration files that may contain API keys and credentials.
CVSS v4.0
Score 8.7high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability CVE-2026-62230 affects Grav versions before 2.0.4. The default .htaccess file shipped with these versions contains rules to block access to sensitive file types but does not use the [NC] flag, making the extension matching case-sensitive. On case-insensitive filesystems, this allows an unauthenticated attacker to bypass access restrictions by requesting files with uppercase or mixed-case extensions, potentially exposing sensitive configuration files containing secrets such as API keys and credentials.
Potential Impact
An unauthenticated attacker can bypass .htaccess restrictions on sensitive file types by exploiting case sensitivity issues on case-insensitive filesystems. This can lead to unauthorized disclosure of sensitive configuration files, including those containing API keys and credentials, potentially compromising the security of the affected system.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider manually updating the .htaccess rules to include the [NC] flag for extension matching to enforce case-insensitive blocking of sensitive file types. Monitoring vendor communications for an official patch or update is recommended.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-13T16:40:10.961Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a59784168715ace4305da5a
Added to database: 07/17/2026, 00:33:05 UTC
Last enriched: 07/17/2026, 00:48:09 UTC
Last updated: 07/17/2026, 01:45:06 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.