CVE-2026-100669

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Grav before 2.0.25 ships web server configuration samples whose access-control deny rules are matched case-sensitively. In webserver-configs/web.config (IIS), every deny rule (user_sensitive_folders, user_accounts, user_data, user_error_redirect, user_pages, system, vendor, ignore_folders) sets ignoreCase="false" on its URL Rewrite element, overriding the IIS default of ignoreCase="true"; because these are rewrite matches rather than elements, there is no case-insensitive fallback. On IIS running over case-insensitive NTFS, an unauthenticated remote attacker can vary the case of a folder name or file extension (for example GET /user/CONFIG/system.YAML) so that no deny rule matches and the IIS static file handler resolves and returns the underlying file, disclosing sensitive data such as configuration secrets or account password hashes. Whether a bypassed file is actually returned depends on MIME registration: .json is served by default, while .yaml/.yml return HTTP 404.3 on a stock IIS unless a YAML MIME mapping has been added. The same class of gap exists in the bundled webserver-configs/lighttpd.conf, whose user/(config|env), directory, script-extension, root-file and dotfile rules lack the (?i) modifier, though it is lower risk because lighttpd typically runs on case-sensitive filesystems. Deployments served by Apache (.htaccess), nginx, Caddy, or the PHP built-in server are not affected. The issue is fixed in 2.0.25; because the .htaccess installer heal does not touch web.config or lighttpd.conf, operators must re-copy the corrected sample files after upgrading.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
65
EG Risk 65/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 26, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 26, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

Grav before 2.0.25 Sensitive File Disclosure via Case-Variation Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/grav-before-2.0.25-sensitive-file-disclosure-via-case-variation-bypass
github Patch Available🟡 PoC Available

Grav bundled IIS web.config (and lighttpd.conf) case-sensitive deny rules allow case-variation bypass and sensitive file disclosure · Advisory · getgrav/grav · GitHub

https://github.com/getgrav/grav/security/advisories/GHSA-pg8v-xw58-frq8

Vendor Advisories for CVE-2026-100669(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 32× in last 7d / 38× 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-10-04 13:07 UTCGHSA enrichment
  2. 2026-10-04 02:10 UTCGHSA enrichment
  3. 2026-10-03 15:13 UTCEG score recompute
  4. 2026-10-03 15:13 UTCGHSA enrichment
  5. 2026-10-03 14:25 UTCEPSS rescore
  6. 2026-10-03 04:17 UTCGHSA enrichment
  7. 2026-10-02 17:20 UTCEG score recompute
  8. 2026-10-02 17:20 UTCGHSA enrichment
  9. 2026-10-02 06:21 UTCEG score recompute
  10. 2026-10-02 06:20 UTCGHSA enrichment
  11. 2026-10-01 19:49 UTCEPSS rescore
  12. 2026-10-01 19:24 UTCGHSA enrichment
  13. 2026-10-01 08:26 UTCGHSA enrichment
  14. 2026-09-30 21:30 UTCEG score recompute
  15. 2026-09-30 21:30 UTCGHSA enrichment
  16. 2026-09-30 20:27 UTCEG score recompute
  17. 2026-09-30 20:27 UTCGHSA enrichment
  18. 2026-09-30 17:08 UTCEG score recompute
  19. 2026-09-30 17:08 UTCGHSA enrichment
  20. 2026-09-30 15:02 UTCEPSS rescore
  21. 2026-09-30 06:10 UTCGHSA enrichment
  22. 2026-09-29 19:13 UTCEG score recompute
  23. 2026-09-29 19:13 UTCGHSA enrichment
  24. 2026-09-29 15:20 UTCEPSS rescore
  25. 2026-09-29 08:14 UTCEG score recompute
Show 13 more
  1. 2026-09-29 08:14 UTCGHSA enrichment
  2. 2026-09-28 21:18 UTCEG score recompute
  3. 2026-09-28 21:18 UTCGHSA enrichment
  4. 2026-09-28 13:50 UTCEPSS rescore
  5. 2026-09-28 10:21 UTCGHSA enrichment
  6. 2026-09-27 23:25 UTCEG score recompute
  7. 2026-09-27 23:25 UTCGHSA enrichment
  8. 2026-09-27 12:28 UTCGHSA enrichment
  9. 2026-09-27 01:31 UTCEG score recompute
  10. 2026-09-27 01:31 UTCGHSA enrichment
  11. 2026-09-26 14:33 UTCEG score recompute
  12. 2026-09-26 13:37 UTCEG score recompute
  13. 2026-09-26 13:30 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-100669?
CVE-2026-100669 is a high vulnerability published on September 26, 2026. Grav before 2.0.25 ships web server configuration samples whose access-control deny rules are matched case-sensitively. In webserver-configs/web.config (IIS), every deny rule (usersensitivefolders, useraccounts, userdata, usererrorredirect, userpages, system, vendor, ignorefolders) sets…
When was CVE-2026-100669 disclosed?
CVE-2026-100669 was first published on September 26, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-100669 actively exploited?
CVE-2026-100669 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100669?
CVE-2026-100669 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100669?
A fix for CVE-2026-100669 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100669 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-100669?

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

Book a Demo →Browse All CVEs