CVE-2026-127060: @fastify/http-proxy vulnerable to prefix escape via semicolon path-parameter dot-segments
@fastify/http-proxy is a Fastify plugin that proxies HTTP and WebSocket traffic to an upstream server. In versions before 11.6.10, it rejects destinations containing parent-directory path segments by an exact string match, so a segment that carries a semicolon path parameter, such as a dot-dot segment followed by a semicolon and an optional parameter, is not equal to the plain dot-dot form and passes the check, and the WHATWG URL parser keeps it as an ordinary segment so the rewrite-prefix containment check also passes. Servlet containers such as Apache Tomcat and Jetty strip semicolon path parameters from each segment before resolving dot-segments, so a request routed through the configured prefix is rewritten and reaches the upstream where it resolves above the intended subtree, escaping the path the proxy is meant to expose and, on some containers, crossing application contexts. Both the HTTP and WebSocket proxy paths are affected. The issue is fixed in @fastify/http-proxy 11.6.10, and users should upgrade to 11.6.10 or later.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/@fastify/http-proxyto a version that resolves this vulnerability.Fixed in 11.6.10
Event History
Frequently Asked Questions
Which deployments are realistically exposed?
Deployments using @fastify/http-proxy before 11.6.10 are exposed when the proxy routes requests through a configured prefix to an upstream servlet container that strips semicolon path parameters before resolving dot-segments, such as Apache Tomcat or Jetty. Both HTTP and WebSocket proxy routes are affected.
What does an attacker need to exploit this?
The attacker needs network access to send a request to an affected proxy route. They can use a path containing a parent-directory segment with a semicolon path parameter, allowing the request to pass the proxy checks and then be resolved above the intended upstream subtree.
What should be done if the proxy is in use?
Upgrade @fastify/http-proxy to version 11.6.10 or later. The provided information does not describe an alternative mitigation for deployments that cannot upgrade immediately.
How can I determine whether my service may already be affected?
Check whether the application uses @fastify/http-proxy before 11.6.10 and proxies to a servlet-based upstream such as Apache Tomcat or Jetty. Review both HTTP and WebSocket proxy paths, especially routes intended to restrict access to a specific upstream path prefix.