Skip to main content
CVE-2026-55458VulnerabilityPublished Updated

caddy · Prior to 2.11.5, the reverse proxy's finalizeResponse method in modules/caddyhttp/reverseproxy/reverseproxy.go handles

Affects caddySource GCVE Database

0
Compare
Authoritative record:CVE-2026-55458· Low 2.9

Public exploit available · CVSS 2.9 Low · fixed in 2.11.5 : patch caddy as a priority.

Data as of 18 Nov 2026, 15:19 UTC

CVSS 4.0 base score
2.9Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.02.9
Patch
Available – fixed in 2.11.5
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Ubuntu 26.10caddypkg:deb/ubuntu/caddy?arch=source&distro=stonkingOther threatsAffected
  • =2.6.2-14
  • =2.11.4-1
Fixed in–
Ubuntu Pro 26.04 LTScaddypkg:deb/ubuntu/caddy?arch=source&distro=esm-apps/resoluteOther threatsAffected
  • =2.6.2-12
  • =2.6.2-14
  • =2.6.2-14ubuntu0.26.04.1~esm1
Fixed in–
Ubuntu Pro 24.04 LTScaddypkg:deb/ubuntu/caddy?arch=source&distro=esm-apps/nobleOther threatsAffected
  • 2.6.2-6 – 2.6.2-6ubuntu0.24.04.3+esm2
7 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

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.

References

Community reviews

Loading reviews…