CVE-2026-62230
Unauthenticated file disclosure via case-sensitive .htaccess rules on Grav sites
Is CVE-2026-62230 being exploited?
Not confirmed. CVE-2026-62230 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.48% probability of exploitation in the next 30 days.
How severe is CVE-2026-62230?
CVE-2026-62230 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-62230?
Yes. A fix has been recorded for CVE-2026-62230. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-62230 affect?
CVE-2026-62230 affects Grav CMS < 2.0.4, Sites using Grav's default .htaccess, Hosts on case-insensitive filesystems (Windows NTFS, macOS HFS+, Docker volume mounts). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-62230?
Upgrade to Grav 2.0.4+ or update .htaccess to use case-insensitive rules and restrict config file access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attackers can read sensitive config files (API keys, credentials) by requesting mixed/upper-case extensions on case-insensitive filesystems.
Immediate action required
- affected< 2.0.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.