high CVSS 8.1 EPSS 0.36%

CVE-2026-30851·Caddy vulnerability

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

Severity
high
Software
Caddy
Fixed in
2.11.2
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.36% — higher than 28% 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-30851 scores 8.1 on CVSS, so a successful attack would be serious — but at 0.36%, 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.0

Until: 2.11.2

Fixed in: 2.11.2

How to fix this CVE

Upgrade Caddy to version 2.11.2 or later to address a header injection vulnerability in the forward_auth middleware's copy_headers directive. This vulnerability allows authenticated attackers to inject arbitrary headers and escalate privileges by bypassing proper header sanitization. Immediate patching is recommended for any Caddy instance using the forward_auth directive with header copying enabled.

sudo dnf update caddy

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

POST|GET.*\bAuthorization\b.*:\s*Bearer\s+[^\s]+|X-Remote-User\s*:\s*(?!^[a-zA-Z0-9._-]+$)|X-Auth.*:\s*.*['\"].*['\"]

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 sanitize requests containing suspicious Authorization, X-Remote-User, or X-Auth-* headers with special characters, quotes, or encoded payloads. Implement strict header validation rules that only allow alphanumeric characters, hyphens, and underscores in authentication-related headers forwarded to backend services.

How to check if you are affected

  1. Step 1: Check the installed Caddy version by running: caddy version
  2. Step 2: Review your Caddyfile for forward_auth directives with copy_headers configuration: grep -n 'forward_auth\|copy_headers' /etc/caddy/Caddyfile
  3. Step 3: Search access logs for suspicious header values or authentication bypass attempts: grep -i 'authorization\|x-remote-user\|x-auth' /var/log/caddy/access.log | grep -v 'GET\|POST' | head -20
  4. Step 4: Verify the patch by running caddy version and confirming the version is 2.11.2 or later

FAQ

What is CVE-2026-30851?

This vulnerability affects Caddy's forward_auth middleware, where the copy_headers feature fails to properly sanitize client-supplied headers before forwarding them to backend authentication services. An authenticated attacker can inject malicious header values to impersonate other users or gain elevated privileges.

Is CVE-2026-30851 being actively exploited?

No, this vulnerability is not currently listed on the CISA KEV catalog and no public exploits are available. However, the attack requires only low complexity and authenticated access, making it a medium-term risk for exposed Caddy instances.

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

Caddy versions 2.10.0 through 2.11.1 are vulnerable. The issue is resolved in version 2.11.2 and all later releases.

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

Run caddy version to check your installed version. If it is between 2.10.0 and 2.11.1 inclusive, and your Caddyfile contains forward_auth with copy_headers enabled, your system is vulnerable.

Does Defensia detect CVE-2026-30851?

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

Get started free