CVE-2026-55458
Caddy is an extensible server platform that uses TLS by default. …
Caddy is an extensible server platform that uses TLS by default. Prior to 2.11.5, the reverse proxy's finalizeResponse method in modules/caddyhttp/reverseproxy/reverseproxy.go handles an upstream 101 Switching Protocols response before running removeConnectionHeaders and the hopHeaders deletion loop used for ordinary responses. The early return invokes handleUpgradeResponse, which copies the upstream headers to the client and normalizes only WebSocket-specific header names. An attacker who controls or compromises a proxied WebSocket upstream can therefore cause hop-by-hop headers such as Alt-Svc, Keep-Alive, and Proxy-Authenticate, as well as headers named by Connection, to cross the proxy boundary. For HTTP/2 or HTTP/3 extended CONNECT, the upstream 101 response may be represented to the client as an ordinary successful response, increasing the chance that leaked headers are processed. This issue is fixed in version 2.11.5.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/caddyserver/caddy/security/advisories/GHSA-8qx7-j2v2-x6q5
- github.com/caddyserver/caddy/releases/tag/v2.11.5
- github.com/advisories/GHSA-8qx7-j2v2-x6q5
- github.com/caddyserver/caddy/commit/25b3eab6dbd8d2d2670711f26b774e0fd43e1179
- nvd.nist.gov/vuln/detail/CVE-2026-55458
- cve.org/CVERecord?id=CVE-2026-55458
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.