Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Thu, 03 Sep 2026 16:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Fastify
Fastify fastify-http-proxy |
|
| Vendors & Products |
Fastify
Fastify fastify-http-proxy |
Thu, 03 Sep 2026 13:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 03 Sep 2026 11:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | @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. | |
| Title | @fastify/http-proxy vulnerable to prefix escape via backslash dot-segments | |
| Weaknesses | CWE-22 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: openjs
Published:
Updated: 2026-09-03T12:32:56.358Z
Reserved: 2026-09-03T08:15:18.564Z
Link: CVE-2026-85124
Updated: 2026-09-03T12:32:49.123Z
Status : Undergoing Analysis
Published: 2026-09-03T13:06:21.773
Modified: 2026-09-03T18:11:49.487
Link: CVE-2026-85124
No data.
OpenCVE Enrichment
Updated: 2026-09-03T15:33:17Z