Back

HIGH

@fastify/http-proxy vulnerable to prefix escape via backslash dot-segments

Published Sep 3, 2026

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.

Affected products

Remediation

Red Hat statement

This Important flaw in `@fastify/http-proxy` allows an unauthenticated network attacker to bypass proxy path validation using backslash dot-segments. This can lead to information disclosure by enabling access to internal endpoints that should be protected by the proxy, impacting the confidentiality of sensitive data within affected Red Hat products.

Red Hat mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Weaknesses (1)

References (7)

Change history (0)

No recorded changes yet.

Sources

CVE.org / MITRE

Status PUBLISHED
Assigner openjs
Published Sep 3, 2026
Updated Sep 3, 2026
Reserved Sep 3, 2026

CISA Vulnrichment

Updated Sep 3, 2026

NVD

Status Analyzed
Modified Sep 9, 2026

Red Hat

Severity Important
Public date Sep 3, 2026
Bugzilla 2527955

ENISA EUVD

Assigner openjs
Published Sep 3, 2026
Updated Sep 3, 2026

GitHub

No data