@fastify/http-proxy versions before 11.6.2 do not validate proxied HTTP request paths for backslash based dot-segments before forwarding them to the configured upstream. The plain HTTP request handler skips the destination validation that the WebSocket path performs, and the underlying reply-from library only rejects forward-slash traversal, so a request containing backslash dot-segments can escape the boundary set by the prefix and rewritePrefix options. An unauthenticated network attacker can use this to reach upstream paths that were meant to stay hidden behind the proxy, resulting in disclosure of internal endpoints. This is a path traversal issue (CWE-22). Users should upgrade to @fastify/http-proxy 11.6.2 or later.
References
| Link | Resource |
|---|---|
| https://cna.openjsf.org/security-advisories.html | Third Party Advisory |
| https://github.com/fastify/fastify-http-proxy/security/advisories/GHSA-qv33-689p-2xq5 | Vendor Advisory |
Configurations
History
No history.
Information
Published : 2026-09-03 13:06
Updated : 2026-09-09 19:25
NVD link : CVE-2026-85124
Mitre link : CVE-2026-85124
CVE.ORG link : CVE-2026-85124
JSON object : View
Products Affected
fastify
- fastify\/http-proxy
CWE
CWE-22
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
