Fastify proxy path escape affects applications that use two Fastify packages to confine requests to an upstream prefix. Fastify published separate advisories on November 19, 2026, for CVE-2026-127064 and CVE-2026-127060. The immediate task is to identify proxy routes backed by Java servlet containers and update the relevant packages.
The boundary fails when the Fastify side and servlet side interpret a path segment differently. Fastify’s checks can accept a segment carrying a semicolon path parameter, while the servlet removes that parameter before resolving the path. A route intended to expose one subtree can then reach another. The advisories describe possible access to hidden administrative or internal routes, including state-changing requests.
Fastify Proxy Path Escape: Which Deployments Need This Playbook?
Start with the application dependency tree and the actual upstream for each proxy route. The reply-from advisory covers versions before 12.8.4. The http-proxy advisory covers versions before 11.6.10. These are separate packages and separate CVEs, so check both even when a service declares only one directly.
Exposure requires an upstream that strips semicolon path parameters before resolving parent-directory segments. Fastify identifies Apache Tomcat, Jetty, WildFly and Spring Boot servlet deployments as relevant to the reply-from issue. Its http-proxy advisory specifically names Tomcat, Jetty and embedded servlet containers. The same advisory says Spring applications using Spring Security’s StrictHttpFirewall reject semicolons and are unaffected by that described route.
Fastify says Node.js, nginx and Express upstreams do not have this particular interpretation conflict. Confirm each route’s real upstream before excluding it. A proxy may point to a gateway that forwards again to a servlet application. Record the full path from public Fastify listener to the component that finally resolves the request.
What Should the Response Team Do First?
Work from exposed routes to deployed versions, then verify the boundary after patching. The vulnerability intelligence platform page gives related product context; record package findings and remediation owners in your service inventory. The order below is our operational reading of Fastify’s two advisories, rather than a vendor incident response procedure.
- InventoryIdentify each Fastify service, deployed package version, proxy prefix, rewrite rule and final upstream.
- PrioritizePut internet-facing routes to servlet backends first, especially where a prefix hides administrative or internal functions.
- UpdateDeploy reply-from 12.8.4 and http-proxy 11.6.10 where those packages are present.
- VerifyConfirm the running dependency versions and test that allowed routes work while out-of-scope routes stay inaccessible.
- ReviewCompare proxy and servlet access logs for unexpected crossings of the intended route boundary.
The inventory step matters because a package can be present without a vulnerable servlet-backed route. It also prevents a false sense of safety from checking the Fastify service alone. Capture the deployed lockfile or package inventory, the running build identifier and the upstream type for each route. Keep that evidence with the remediation ticket.
The vulnerability management workflow can track owner, priority and closure evidence across the services. Treat a dependency upgrade as complete only after the deployed service uses the fixed version. A committed version change does not prove that every running instance restarted or received the same build.
Why Do HTTP and WebSocket Routes Need Separate Checks?
The two advisories describe related parsing failures, but their request paths are not identical. For ordinary HTTP through http-proxy, reply-from also validates the forwarded request. WebSocket upgrades go directly through http-proxy’s destination validation, according to Fastify. Inspect both route types where WebSocket proxying is enabled.
For reply-from, Fastify says non-GET methods can also pass through the affected proxy path. That matters when a hidden route changes application state. Review whether the upstream independently authenticates and authorizes those routes. A proxy prefix should not be the sole control for an administrative action.
Fastify verified the reply-from behavior against Apache Tomcat 9.0.123. That test supports the described mechanism; it does not establish that every Java deployment has the same configuration or exposure. The http-proxy advisory also says the path can cross web application contexts on Tomcat. Model the trust boundary at the actual servlet deployment, not only in Fastify configuration.
How Can Teams Reduce Exposure Before the Rollout Finishes?
Fastify lists two temporary measures: reject requests whose decoded path contains a semicolon before proxying, or configure the servlet upstream to reject path parameters. Choose a measure that fits the application’s legitimate traffic. Matrix parameters may be in normal use, so test expected requests before enabling a blanket rejection.
Put this change at the public-facing route and cover both HTTP and WebSocket handling where applicable. Record the exact configuration and when it was enabled. After the package updates, retest legitimate routes, the intended prefix boundary and authorization on sensitive upstream routes. Remove a temporary rule only after the fixed build and boundary tests are confirmed.
Use access logs to investigate requests that appear to cross the intended prefix or reach sensitive servlet routes through the proxy. Preserve relevant proxy and upstream timestamps so investigators can correlate a request across both layers. These are suggested review steps; the Fastify advisories do not publish a detection signature or claim an incident in your environment.
What Does the November 19 Evidence Say About Exploitation?
Fastify rates CVE-2026-127064 High with CVSS 3.1 score 8.2. It rates CVE-2026-127060 Moderate with CVSS 3.1 score 6.5. The advisories and available NVD record do not give CVSS 4.0 scores. CISA’s catalog version 2026.11.18 did not list either CVE when the source pack checked it on November 19.
Fastify’s advisories describe a path escape, but do not confirm exploitation in a named environment. Base response priority on verified route exposure.
Prioritize from your own exposure: public route, vulnerable deployed package, servlet parsing behavior and a protected upstream function. A lower advisory score does not make a WebSocket route safe when its actual controls depend on the proxy prefix. Close the response with a patch management process that records versions, route tests and the owner who verified them.
Frequently Asked Questions
Which Fastify versions should teams deploy?
Deploy @fastify/reply-from 12.8.4 and @fastify/http-proxy 11.6.10 where those packages are used. Confirm each running service loads the fixed versions.
Are Node.js or nginx upstreams affected by this path escape?
Fastify says Node.js, nginx and Express upstreams are unaffected by this specific semicolon path interpretation conflict. Verify the final upstream for each route.
Should teams inspect WebSocket routes too?
Yes. Fastify says WebSocket upgrades through http-proxy rely on its destination validation. Inspect enabled WebSocket proxy routes and test their intended boundaries after patching.
