{"schema":"threatline.record/2","record":{"id":"CVE-2026-100669","aliases":["GHSA-pg8v-xw58-frq8"],"summary":"Grav before 2.0.25 Sensitive File Disclosure via Case-Variation Bypass","details":"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.","categories":["Unclassified"],"product":"grav","vendor":"getgrav","ecosystem":null,"affected_ranges":[{"source":"CVE List","source_url":"https://www.cve.org/CVERecord?id=CVE-2026-100669","source_modified_at":"2026-09-30T20:11:12.856Z","fetched_at":"2026-10-23T18:52:38.922436Z","product":"grav","vendor":"getgrav","versions":[{"version":"0","status":"affected","versionType":"semver","lessThan":"2.0.25"},{"version":"2.0.25","status":"unaffected","versionType":"semver"}],"defaultStatus":"unaffected"}],"fixed_versions":[{"source":"CVE List","source_url":"https://www.cve.org/CVERecord?id=CVE-2026-100669","source_modified_at":"2026-09-30T20:11:12.856Z","fetched_at":"2026-10-23T18:52:38.922436Z","package":{"name":"grav","ecosystem":null},"version":"2.0.25","basis":"first unaffected version stated in the CVE record"}],"cvss":8.7,"severity":"High","kev":{"listed":false},"epss":{"probability":0.00443,"percentile":0.37567,"score_date":"2026-10-23"},"published_at":"2026-09-26T13:23:34.082Z","modified_at":"2026-09-30T20:11:12.856Z","provenance":[{"source":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-100669","fetched_at":"2026-10-23T18:52:38.922436Z","source_modified_at":"2026-09-30T20:11:12.856Z"},{"source":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-100669","fetched_at":"2026-10-23T18:42:43.628194Z","source_modified_at":"2026-10-23"}],"sources":["CVE List","EPSS"],"references":[{"source":"CVE List","url":"https://github.com/getgrav/grav/security/advisories/GHSA-pg8v-xw58-frq8","tags":["vendor-advisory"]},{"source":"CVE List","url":"https://www.vulncheck.com/advisories/grav-before-2.0.25-sensitive-file-disclosure-via-case-variation-bypass","tags":["third-party-advisory"]}],"locations":[],"motoko_assessment":{"status":"requires_architecture_review","automatic_remediation":false},"cve_state":"PUBLISHED","cvss_source":"CVE List","ssvc":{"exploitation":"poc","automatable":"yes","technical_impact":"partial","assessed_at":"2026-09-30T18:44:31.966178Z"},"classification":{"method":"product-first software-layer rules","rules_version":"2.1","matched_on":null,"confidence":"unknown","reviewed":false},"change_timestamp":"2026-09-30T20:11:12.856Z","content_hash":"48610f0d26de857672667192dced63fbdb573628a3354553ba990d5b9120cded"}}