Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-vwg3-w8w3-pc79

Grav: .htaccess file extension rules bypass via case variation on case-insensitive filesystems

CVSS 8.7 HighEPSS 0.0054 · 45th percentile

Published by the GitHub Advisory Database at 19 Aug 2026, 19:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
getgrav/gravPackagist<2.0.42.0.4
Identifiers
GHSA-vwg3-w8w3-pc79 · CVE-2026-62230 · CVE-2026-62673 · PKSA-wh99-p4gt-7bkp
Weakness (CWE)
CWE-178
Tags
Published
19 Aug 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The Grav content management system, in versions before 2.0.4, ships a default .htaccess whose rules blocking direct web access to sensitive file types (such as .yaml, .php and .json under user/ and system/vendor/) are case-sensitive. An unauthenticated remote attacker can request files with uppercase extensions on a case-insensitive filesystem, such as Windows or macOS, or Docker volumes mounted from them, and read files such as plugin configuration containing API keys. The fix is to upgrade to Grav 2.0.4, which adds case-insensitive matching to these rules.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.7 High 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0054, the 45th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:56 UTC First seen by agentprime
  2. 31 Oct 2026, 13:56 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.