critical CVSS 9.1 EPSS 0.55%

CVE-2026-27588·Caddy vulnerability

Caddy 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.

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.55% — higher than 45% 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-27588 scores 9.1 on CVSS, so a successful attack would be serious — but at 0.55%, 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

From: 2.10.2

Until: 2.11.1

Fixed in: 2.11.1

How to fix this CVE

Upgrade Caddy to version 2.11.1 or later to resolve a critical host matching inconsistency that allows attackers to bypass routing rules through HTTP header case manipulation. Organizations running Caddy 2.10.2 through 2.11.0 with host-based access controls should prioritize this update immediately, as the vulnerability affects all configurations using large host lists (over 100 entries). After upgrading, verify that host matching behavior is consistent regardless of header casing and re-test any dependent access control policies.

sudo dnf update -y caddy

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

Host: [A-Z][a-zA-Z0-9.-]* requests targeting a configured domain where casing differs from the Caddyfile definition, combined with successful bypass of routing rules (HTTP 200/301 instead of expected 403/404), indicates potential exploitation.

WAF mitigation (if patching is not yet possible)

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

Implement a WAF rule that normalizes all incoming Host headers to lowercase before Caddy processing, or enforce strict Host header validation by whitelisting only exact case-sensitive matches during the interim period before patching.

How to check if you are affected

  1. Step 1: Check the running Caddy version with `caddy version` or `caddy -version`
  2. Step 2: Examine your Caddyfile or JSON configuration for `host` matchers with more than 100 entries using `grep -c 'host' /etc/caddy/Caddyfile` or by reviewing the config structure
  3. Step 3: Search access logs for requests with Host headers matching your configured hosts but in different casing than defined (e.g., log entries showing mixed case variants like 'Example.com' vs 'example.com')
  4. Step 4: After upgrading to 2.11.1, run `caddy version` again to confirm the update and restart the service with `sudo systemctl restart caddy`, then test host matching with `curl -H 'Host: EXAMPLE.COM' https://your-domain/` to verify rejection of mismatched cases

FAQ

What is CVE-2026-27588?

CVE-2026-27588 is a critical vulnerability in Caddy's HTTP host request matcher where an optimization path for large host lists (>100 entries) inadvertently breaks the documented case-insensitive matching behavior, allowing attackers to bypass host-based access controls by altering the casing of the Host HTTP header.

Is CVE-2026-27588 being actively exploited?

No. As of the current advisory, CVE-2026-27588 is not listed on the CISA Known Exploited Vulnerabilities catalog, and no public exploit code has been released.

What versions of Caddy are affected by CVE-2026-27588?

Caddy versions 2.10.2 through 2.11.0 are affected. The vulnerability is fixed in version 2.11.1 and later.

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

Run `caddy version` to determine the installed version. If it falls between 2.10.2 and 2.11.0, and your Caddyfile contains a host matcher with more than 100 entries, your server is vulnerable. Check your config with `grep -c 'host' /etc/caddy/Caddyfile` to count entries.

Does Defensia detect CVE-2026-27588?

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

Related Caddy CVEs

CVE-2026-27590CVSS 9.8Caddy 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.
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-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-52845CVSS 8.1Caddy is an extensible server platform that uses TLS by default. Prior to 2.11.4, forward_auth copy_headers deletes the exact client-supplied identity header before copying the trusted value from the auth gateway. But when the request later goes through php_fastcgi, Caddy normalizes HTTP headers into CGI variables by replacing - with _. This lets a client send an underscore alias that survives the forward_auth delete step but becomes the same PHP/FastCGI variable. Result: a remote client can inject or sometimes override identity/group headers trusted by PHP/FastCGI applications behind Caddy. This vulnerability is fixed in 2.11.4.
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.

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-27588. Free for 1 server.

Get started free