Skip to main content
VulnerabilityPublished Updated

CVE-2026-27585: caddyserver caddy · Improper Input Validation

Affects caddyserver caddySource CVE Database V5

0
Compare

Public exploit available · CVSS 6.9 Medium : upgrade to 2.11.1 as a priority.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.11.1
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade caddy and caddyserver/caddy to 2.11.1.

Affected software

ProductAffectedFixed in
caddyservercaddyAffected
  • <2.11.1
Fixed in
  • 2.11.1
GitHubcaddyserver/caddypkg:github/caddyserver/caddyOther threatsAffected
  • <2.11.1
Fixed in
  • 2.11.1

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

AI-suggested

  1. Upgrade all Caddy server instances to version 2.11.1 or later immediately to ensure the path sanitization routine properly handles backslashes.
  2. Review and audit any custom configurations or plugins that interact with file paths to ensure they do not rely solely on Caddy's sanitization and implement additional input validation if necessary.
  3. Implement strict access controls and file system permissions to limit the impact of any potential path traversal or bypass attempts.
  4. Monitor web server logs for suspicious requests containing backslashes or unusual path patterns that could indicate exploitation attempts.
  5. Employ web application firewalls (WAFs) with rules designed to detect and block path traversal or malformed path requests targeting Caddy servers.
  6. Conduct regular security assessments and penetration testing focusing on path traversal and input validation weaknesses in your web infrastructure.
  7. Educate development and operations teams about the importance of input validation and patch management to prevent similar vulnerabilities.

Description

Caddy is an extensible server platform that uses TLS by default. Prior to version 2.11.1, the path sanitization routine in file matcher doesn't sanitize backslashes which can lead to bypassing path related security protections. It affects users with specific Caddy and environment configurations. Version 2.11.1 fixes the issue.

References

Community reviews

Loading reviews…