CVE-2026-55458

GHSA-8qx7-j2v2-x6q5 · GO-2026-6874 · published 28 Oct 2026 · updated 12 Nov 2026

Caddy: RFC 7230 §6.1 compliance issue / Hop-by-hop headers that leak through

2.9LowCVSS 2.9EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in github.com/caddyserver/caddy/v2 2.11.5.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
caddyserver<2.11.5
go: github.com/caddyserver/caddy/v2<2.11.52.11.5

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-55458 severity on Zeptric[![CVE-2026-55458](https://zeptric.io/badge/cve/CVE-2026-55458.svg)](https://zeptric.io/cve/CVE-2026-55458)