critical CVSS 9.8 EPSS 0.19%

CVE-2026-27590·Caddy vulnerability

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.

Severity
critical
Software
Caddy
Fixed in
2.11.1
Published

How likely is exploitation

FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.19% — higher than 41% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.

Read the two together. CVE-2026-27590 scores 9.8 on CVSS, so a successful attack would be serious — but at 0.19%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.

Affected versions

Until: 2.11.1

Fixed in: 2.11.1

How to fix this CVE

Update PHP to version 2.11.1 or later to resolve a critical Unicode path-handling vulnerability in FastCGI configurations. This flaw could allow attackers to execute unintended PHP files through byte-length misalignment when processing non-ASCII characters in request paths, particularly in systems with file upload capabilities. Immediate patching is strongly recommended for all production environments running vulnerable versions.

sudo dnf update php

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

POST|GET request with UTF-8 multi-byte characters (e.g., %C3%A9, %E2%80%A6) in the path segment preceding .php filename, followed by execution of non-.php file types (e.g., .txt, .jpg, .conf)

WAF mitigation (if patching is not yet possible)

Add this rule to your WAF to block exploitation attempts while you schedule the patch.

Implement request normalization rules that decode and validate UTF-8 sequences before path processing. Block requests containing multi-byte Unicode sequences in FastCGI script paths. Additionally, enforce strict file-type validation to prevent execution of non-script files via PATH_INFO manipulation.

How to check if you are affected

  1. Step 1: Check installed PHP version with: php --version or php -v
  2. Step 2: Verify FastCGI is enabled in your Caddy configuration by checking caddy.conf or running: caddy list-modules | grep fastcgi
  3. Step 3: Search web server logs for requests containing non-ASCII/Unicode characters followed by .php extensions: grep -E '[\x80-\xFF].*\.php' /var/log/caddy/access.log
  4. Step 4: Confirm patch application by verifying the updated PHP version matches 2.11.1 or later: php --version

FAQ

What is CVE-2026-27590?

A critical vulnerability in Caddy's FastCGI handler that miscalculates script path boundaries when Unicode characters are present, causing byte-index misalignment between lowercased and original request paths. This can redirect PHP execution to unintended files, enabling remote code execution in upload-enabled deployments.

Is CVE-2026-27590 being actively exploited?

No, this vulnerability is not currently listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, and no public exploits are available. However, the critical severity score (9.8) and RCE potential warrant immediate patching.

What versions of PHP are affected by CVE-2026-27590?

All versions of PHP prior to 2.11.1 are affected. The vulnerability exists in Caddy's FastCGI path-splitting logic, not PHP itself, but impacts PHP execution contexts when Caddy is used as the application server.

How do I check if my server is vulnerable to CVE-2026-27590?

Run php --version to confirm your installed version is below 2.11.1. Additionally, check if FastCGI is active in your Caddy configuration with: grep -i fastcgi /etc/caddy/caddy.conf or caddy list-modules | grep fastcgi.

Does Defensia detect CVE-2026-27590?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If PHP is installed on a monitored server, CVE-2026-27590 will appear in your dashboard with remediation steps.

Related Caddy CVEs

CVE-2026-27586CVSS 9.1Caddy is an extensible server platform that uses TLS by default. Prior to version 2.11.1, two swallowed errors in `ClientAuthentication.provision()` cause mTLS client certificate authentication to silently fail open when a CA certificate file is missing, unreadable, or malformed. The server starts without error but accepts any client certificate signed by any system-trusted CA, completely bypassing the intended private CA trust boundary. Any deployment using `trusted_ca_cert_file` or `trusted_ca_certs_pem_files` for mTLS will silently degrade to accepting any system-trusted client certificate if the CA file becomes unavailable. This can happen due to a typo in the path, file rotation, corruption, or permission changes. The server gives no indication that mTLS is misconfigured. Version 2.11.1 fixes the vulnerability.
CVE-2026-27588CVSS 9.1Caddy is an extensible server platform that uses TLS by default. Prior to version 2.11.1, Caddy's HTTP `host` request matcher is documented as case-insensitive, but when configured with a large host list (>100 entries) it becomes case-sensitive due to an optimized matching path. An attacker can bypass host-based routing and any access controls attached to that route by changing the casing of the `Host` header. Version 2.11.1 contains a fix for the issue.
CVE-2026-27587CVSS 9.1Caddy is an extensible server platform that uses TLS by default. Prior to version 2.11.1, Caddy's HTTP `path` request matcher is intended to be case-insensitive, but when the match pattern contains percent-escape sequences (`%xx`) it compares against the request's escaped path without lowercasing. An attacker can bypass path-based routing and any access controls attached to that route by changing the casing of the request path. Version 2.11.1 contains a fix for the issue.
CVE-2026-45135CVSS 8.1Caddy is an extensible server platform that uses TLS by default. From 2.7.0 until 2.11.3, the FastCGI transport's splitPos() in modules/caddyhttp/reverseproxy/fastcgi/fastcgi.go misuses golang.org/x/text/search with search.IgnoreCase when the request path contains a non-ASCII byte. Two distinct flaws in that fallback let an attacker mislead Caddy's FastCGI splitting into treating a non-.php (or other configured split_path extension) file as a script. In any deployment where the attacker can place content into a file served via FastCGI (uploads, file storage, etc.), this can be escalated to remote code execution by crafting a URL whose path triggers either flaw. This vulnerability is fixed in 2.11.3.
CVE-2026-30851CVSS 8.1Caddy is an extensible server platform that uses TLS by default. From version 2.10.0 to before version 2.11.2, forward_auth copy_headers does not strip client-supplied headers, allowing identity injection and privilege escalation. This issue has been patched in version 2.11.2.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-27590. Free for 1 server.

Get started free