# CVE-2026-92700: Caddy: fileHidden() case-sensitive pattern bypass — exposes "hidden" files via case variation

> Attackers can bypass file hiding rules in Caddy by using case variations, exposing sensitive files intended to be hidden.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/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:** Yes
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-92700, UBUNTU-CVE-2026-92700

## What is CVE-2026-92700?

CVE-2026-92700 is a medium-severity vulnerability in caddyserver caddy, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Caddy is an extensible server platform that uses TLS by default. In version 2.11.3 and earlier, in modules/caddyhttp/fileserver/staticfiles.go, fileHidden() uses case-sensitive filepath.Match checks, so case variants can bypass hide rules on case-insensitive filesystems or when mixed-case paths coexist and expose files intended to be hidden.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-92700 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92700 is a medium-severity vulnerability in caddyserver caddy, published on 23 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-92700 exists.

Affected product: caddyserver caddy. 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-92700/ (Markdown: https://insights.sbomify.com/CVE-2026-92700/index.md)
```

## Sources

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

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