critical CVSS 9.1 EPSS 0.30%

CVE-2026-27586·Caddy vulnerability

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

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.30% — higher than 22% 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-27586 scores 9.1 on CVSS, so a successful attack would be serious — but at 0.30%, 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

Upgrade Caddy to version 2.11.1 or later to fix a critical mTLS authentication bypass where missing or corrupted CA certificate files are silently ignored, causing the server to accept any system-trusted client certificate. This silent failure can go undetected indefinitely, completely defeating your private CA trust boundary. After upgrading, verify that Caddy properly validates CA certificate paths at startup and rejects connections from unauthorized clients.

sudo dnf check-update caddy && sudo dnf update caddy

Defensia detects this vulnerability

How to check if you are affected

  1. Check installed Caddy version: caddy version
  2. Review Caddyfile for mTLS configuration: grep -n 'trusted_ca_cert' /etc/caddy/Caddyfile
  3. Verify CA certificate files exist and are readable: ls -la /path/to/ca/certs && file /path/to/ca/certs
  4. Check Caddy startup logs for errors: journalctl -u caddy -n 50 | grep -i 'cert\|auth\|fail'
  5. Test mTLS enforcement by attempting connection with unauthorized client certificate and verify rejection

FAQ

What is CVE-2026-27586?

This vulnerability causes Caddy to silently ignore missing, unreadable, or malformed CA certificate files used for mutual TLS authentication. Instead of failing securely, the server allows any client certificate signed by a system-trusted CA to be accepted, completely bypassing your intended private CA trust boundary.

Is CVE-2026-27586 being actively exploited?

No, this vulnerability is not currently listed in the CISA Known Exploited Vulnerabilities catalog and no public exploits are available. However, the silent failure nature makes detection difficult, so proactive patching is essential.

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

All versions of Caddy prior to version 2.11.1 are affected. The vulnerability exists in the `ClientAuthentication.provision()` function and affects any deployment relying on `trusted_ca_cert_file` or `trusted_ca_certs_pem_files` directives.

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

Run `caddy version` to check your installed version—if it is below 2.11.1, you are vulnerable. Additionally, verify your Caddyfile contains mTLS directives by running `grep -i 'trusted_ca' /etc/caddy/Caddyfile`.

Does Defensia detect CVE-2026-27586?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Caddy is installed on a monitored server, CVE-2026-27586 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-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-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-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-27586. Free for 1 server.

Get started free