CVE-2026-62230

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-17. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Grav before 2.0.4 ships a default .htaccess (and reference webserver-configs/htaccess.txt) whose rules blocking access to sensitive file types (.yaml, .php, .json, etc.) lack the [NC] flag, making extension matching case-sensitive. On case-insensitive filesystems (Windows/NTFS, macOS/HFS+, or Docker volume mounts), an unauthenticated attacker can request these files with uppercase or mixed-case extensions (e.g., .YAML, .PHP) to bypass the restrictions and read sensitive configuration files that may contain API keys and credentials.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS
20.4%
KEV
Not listed

Published

July 17, 2026

Last Modified

July 17, 2026

Advisory Details (2)

Auto-updated Jul 17, 2026
Patch available. Sources: github.
generic

Grav < 2.0.4 File Access Bypass via Case Variation | Advisories | VulnCheck

https://www.vulncheck.com/advisories/grav-file-access-bypass-via-case-variation
github Patch Available

.htaccess file extension rules bypass via case variation on case-insensitive filesystems · Advisory · getgrav/grav · GitHub

https://github.com/getgrav/grav/security/advisories/GHSA-vwg3-w8w3-pc79

Vendor Advisories for CVE-2026-62230(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 16× in last 7d / 16× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 03:21 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:25 UTCEPSS rescore
  5. 2026-07-21 15:25 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 02:29 UTCEPSS rescore
  9. 2026-07-18 18:41 UTCEG score recompute
  10. 2026-07-18 18:41 UTCGHSA enrichment
  11. 2026-07-18 10:04 UTCEPSS rescore
  12. 2026-07-17 14:51 UTCEG score recompute
  13. 2026-07-17 14:51 UTCGHSA enrichment
  14. 2026-07-17 06:54 UTCGHSA enrichment
  15. 2026-07-17 00:25 UTCEG score recompute
  16. 2026-07-17 00:22 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-62230?
CVE-2026-62230 is a high vulnerability published on July 17, 2026. Grav before 2.0.4 ships a default .htaccess (and reference webserver-configs/htaccess.txt) whose rules blocking access to sensitive file types (.yaml, .php, .json, etc.) lack the [NC] flag, making extension matching case-sensitive. On case-insensitive filesystems (Windows/NTFS, macOS/HFS+, or…
When was CVE-2026-62230 disclosed?
CVE-2026-62230 was first published in the National Vulnerability Database on July 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62230 actively exploited?
CVE-2026-62230 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-62230?
CVE-2026-62230 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-62230?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62230, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-62230

Explore →

Is Your Infrastructure Affected by CVE-2026-62230?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs