HTTP Request Smuggling Affecting caddy package, versions <2.11.6-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.5% (43rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-CADDY-21830910
  • published30 Oct 2026
  • disclosed5 Nov 2026

Introduced: 30 Oct 2026

NewCVE-2026-55458  (opens in a new tab)
CWE-444  (opens in a new tab)

How to fix?

Upgrade Minimos:latest caddy to version 2.11.6-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream caddy package and not the caddy package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1