CVE-2026-27590
Caddy is an extensible server platform that uses TLS by default. …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/caddyserver/caddy/releases/tag/v2.11.1
- github.com/caddyserver/caddy/security/advisories/GHSA-5r3v-vc8m-m96g
- github.com/php/frankenphp/security/advisories/GHSA-g966-83w7-6w38
- nvd.nist.gov/vuln/detail/CVE-2026-27590
- github.com/advisories/GHSA-5r3v-vc8m-m96g
- pkg.go.dev/vuln/GO-2026-4536
- nvd.nist.gov/vuln/detail/CVE-2026-27590
- cve.org/CVERecord?id=CVE-2026-27590
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.