Skip to main content
VulnerabilityPublished Updated

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

Affects caddyserver caddySource CVE Database V5

0
Compare

Public exploit available · CVSS 8.9 High : upgrade to 2.11.1 as a priority.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 4.0 base score
8.9High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% 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:N/PR:N/UI:N/VC:H/VI:H/VA:H/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 29 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 apply the official fix.
  2. Review and restrict file upload functionalities to prevent unauthorized or unvalidated file uploads, especially disallowing upload of files that could be interpreted as executable scripts.
  3. Implement strict input validation and sanitization on all user-supplied data, particularly request paths and filenames.
  4. Employ web application firewalls (WAFs) with rules designed to detect and block suspicious FastCGI requests or path traversal attempts.
  5. Monitor server logs for anomalous requests containing Unicode characters or unusual path patterns that could indicate exploitation attempts.
  6. Consider isolating FastCGI processes and running them with least privilege to limit potential damage from exploitation.
  7. Conduct regular security audits and penetration tests focusing on Unicode handling and path parsing logic in web servers.
  8. Educate developers and administrators about Unicode normalization issues and their security implications to prevent similar vulnerabilities in custom code.

Description

Caddy is an extensible server platform that uses TLS by default. Prior to version 2.11.1, Caddy's FastCGI path splitting logic computes the split index on a lowercased copy of the request path and then uses that byte index to slice the original path. This is unsafe for Unicode because `strings.ToLower()` can change UTF-8 byte length for some characters. As a result, Caddy can derive an incorrect `SCRIPT_NAME`/`SCRIPT_FILENAME` and `PATH_INFO`, potentially causing a request that contains `.php` to execute a different on-disk file than intended (path confusion). In setups where an attacker can control file contents (e.g., upload features), this can lead to unintended PHP execution of non-.php files (potential RCE depending on deployment). Version 2.11.1 fixes the issue.

References

Community reviews

Loading reviews…