high CVSS 8.1 EPSS 0.30%

CVE-2026-52845·Caddy vulnerability

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

Severity
high
Software
Caddy
Fixed in
2.11.4
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-52845 scores 8.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.4

Fixed in: 2.11.4

How to fix this CVE

Update Caddy to version 2.11.4 or later to patch the header normalization vulnerability in the forward_auth module. This vulnerability allows attackers to bypass identity header validation when PHP-FastCGI is used behind Caddy by exploiting HTTP header name normalization (dash-to-underscore conversion). Ensure your web server configuration is reloaded after updating.

sudo dnf update caddy && sudo systemctl restart caddy

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

POST|GET /.*\s HTTP/1\.1.*\n(.*\n)*X_[A-Za-z_-]*:\s.*(identity|user|group|role|uid).*

WAF mitigation (if patching is not yet possible)

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

Block or normalize HTTP requests containing underscore-prefixed header aliases that correspond to known identity headers (e.g., X_FORWARDED_USER, X_REMOTE_USER, X_FORWARDED_GROUPS). Implement request header validation rules that reject requests with both dash and underscore variants of the same header name.

How to check if you are affected

  1. Step 1: Check Caddy version with `caddy version` and confirm it is below 2.11.4
  2. Step 2: Review your Caddyfile configuration for forward_auth directives combined with php_fastcgi handlers
  3. Step 3: Search access logs for suspicious underscore-prefixed HTTP headers (e.g., X_FORWARDED_USER, X_REMOTE_USER) that correspond to dash-based identity headers
  4. Step 4: After updating, verify the patched version with `caddy version` and test header handling with a sample request containing both dash and underscore variants

FAQ

What is CVE-2026-52845?

This vulnerability in Caddy allows unauthenticated clients to inject or override identity headers when forward_auth is used with PHP-FastCGI. The vulnerability stems from Caddy normalizing HTTP header names by converting dashes to underscores, which allows an attacker to bypass the forward_auth header deletion mechanism by supplying an underscore variant of a sensitive header.

Is CVE-2026-52845 being actively exploited?

No, this CVE is not currently listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, and no public exploit code is available. However, the attack is trivial to execute and should be remediated promptly.

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

All versions of Caddy prior to 2.11.4 are affected. Users running Caddy 2.11.4 and later are protected.

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

Run `caddy version` to determine your installed version. If it shows a version below 2.11.4 and your Caddyfile contains both `forward_auth` and `php_fastcgi` directives, your deployment is vulnerable.

Does Defensia detect CVE-2026-52845?

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

Get started free