CVE-2026-27590 Caddy: Unicode case-folding length expansion causes incorrect split_path index in FastCGI transport

High 8.9 Published Updated

Caddy's FastCGI path splitting flaw allows attackers to execute unintended PHP files via Unicode case-folding confusion, potentially leading to remote code execution.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-27590?

CVE-2026-27590 is a high-severity path traversal vulnerability in caddyserver caddy, published on 24 Feb 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. 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.

Weakness: CWE-20, CWE-180

Which versions are affected by CVE-2026-27590?

3 open source packages ship an affected version, including github.com/caddyserver/caddy/v2. It affects 1 product.

PackageAffectedFixed in
github.com/caddyserver/caddy/v2 GoAll versions2.11.1
github.com/caddyserver/caddy/v2 GoAll versions2.11.1
github.com/caddyserver/caddy/v2 GoAll versions2.11.1

Products include Caddyserver Caddy.

How do I fix CVE-2026-27590?

Upgrade github.com/caddyserver/caddy/v2 to 2.11.1 or later.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2026-27590 being exploited?

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

Sources

Also known as DEBIAN-CVE-2026-27590, GHSA-5r3v-vc8m-m96g, GO-2026-4536, MINI-qmpr-6fhp-vvmr, UBUNTU-CVE-2026-27590.

Is CVE-2026-27590 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free