Skip to content

v11.6.10

Latest

Choose a tag to compare

@github-actions github-actions released this 19 Nov 16:43
f5900c0

⚠️ Security Release

This release fixes five vulnerabilities. Four of them affect applications that use websocket: true. The fifth, GHSA-7mjf-mp6r-87p8, affects HTTP and WebSocket proxying to servlet upstreams such as Tomcat or Jetty.

Advisory CVE Severity Affected versions Summary
GHSA-6fhg-8r33-fcww CVE-2026-130647 High >= 9.0.0, < 11.6.10 Denial of Service via a pipelined WebSocket upgrade
GHSA-q659-79j2-32h5 CVE-2026-129500 High >= 9.0.0, < 11.6.10 Denial of Service via an unhandled error on the WebSocket upgrade socket
GHSA-29w6-p7r8-xmf9 CVE-2026-129502 High >= 9.4.0, < 11.6.10 Denial of Service via a URL fragment in a WebSocket upgrade
GHSA-7mjf-mp6r-87p8 CVE-2026-127060 Medium < 11.6.10 Prefix escape via semicolon path-parameter dot-segments
GHSA-w3r4-6w5h-3vrc CVE-2026-133111 Medium >= 7.1.0, < 11.6.10 Cross-Site WebSocket Hijacking via dropped Origin header

Upgrade to @fastify/http-proxy v11.6.10. See each advisory for the workarounds available, if any.

Behavior changes

  • WebSocket upgrades now forward the client's Origin header to the upstream, unless wsClientOptions.origin is set or rewriteRequestHeaders already returns an Origin header. The upstream still receives its own address as Host, so an upstream that requires Origin to match Host must now allow the origins of the clients served by the proxy.
  • Destinations with a .. segment that carries ; path parameters (for example /..;/ or /..;jsessionid=x/) are now rejected. Matrix parameters on other segments are still forwarded unchanged.

What's Changed

Credits

Full Changelog: v11.6.9...v11.6.10