Skip to main content
VulnerabilityPublished

CVE-2026-92700: caddyserver caddy · Improper Handling of Case Sensitivity

Affects caddyserver caddySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium.

Data as of 6 Nov 2026, 23:24 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
caddyservercaddyAffected
  • <=2.11.3
Fixed in–
Gogithub.com/caddyserver/caddypkg:golang/github.com/caddyserver/caddyOther threatsAffected
  • <=2.11.3
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, users should be cautious when deploying caddyserver on case-insensitive filesystems and consider additional access controls or workarounds to prevent exposure of hidden files.

Description

CVE-2026-92700 is a medium severity vulnerability in caddyserver caddy versions 2.11.3 and earlier. It involves improper handling of case sensitivity in the file hiding logic, allowing files intended to be hidden to be exposed on case-insensitive filesystems or when mixed-case paths coexist. This occurs because the fileHidden() function uses case-sensitive filepath.Match checks.

References

Community reviews

Loading reviews…