# CVE-2026-100669: Grav before 2.0.25 Sensitive File Disclosure via Case-Variation Bypass

> Unauthenticated attackers can bypass case-sensitive IIS deny rules to read sensitive configuration files and secrets in Grav CMS deployments.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-cxcx-pfx3-w4vx, GHSA-pg8v-xw58-frq8

## What is CVE-2026-100669?

CVE-2026-100669 is a high-severity vulnerability in getgrav grav, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 <match> element, overriding the IIS default of ignoreCase="true"; because these are rewrite matches rather than <requestFiltering> 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.

Weakness: CWE-178 (Improper Handling of Case Sensitivity)

## Which versions are affected by CVE-2026-100669?


## How do I fix CVE-2026-100669?

No fix has been published for CVE-2026-100669 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-100669 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100669 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-100669 and fix it if it is affected.

What it is: CVE-2026-100669 is a high-severity vulnerability in getgrav grav, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100669 exists.

Affected product: getgrav grav. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-100669/ (Markdown: https://insights.sbomify.com/CVE-2026-100669/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-100669
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-100669
- OSV: https://osv.dev/vulnerability/CVE-2026-100669

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-100669/
Summaries are generated and may contain mistakes; the official description above is the record.