Description
@fastify/http-proxy is a Fastify plugin that proxies HTTP requests to an upstream server under a configured prefix. In versions 11.6.0 through 11.6.2, the destination validation normalizes literal backslashes before it percent-decodes the request path, so a path that encodes its backslashes and dot-segments survives the dot-segment check and is only turned into backslash and double-dot sequences after that check has passed. When the upstream resolves on a platform that treats a backslash as a path separator, the forwarded request walks out of the configured proxy prefix and reaches a sibling location on the upstream. An unauthenticated remote attacker can use this to retrieve upstream resources outside the intended prefix, so the impact is confidentiality only, and exploitation depends on the upstream's path handling. The issue is fixed in @fastify/http-proxy 11.6.3, and users should upgrade to 11.6.3 or later. This is a follow-up to the earlier prefix-escape fix, which did not account for the encoded-backslash form.
Published: 2026-11-02
Score: 5.9 Medium
EPSS: n/a
KEV: No
Impact: Confidentiality Exposure
Action: Upgrade
AI Analysis

Impact

The vulnerability is present in the @fastify/http-proxy plugin, version 11.6.0 through 11.6.2. It allows an unauthenticated remote attacker to manipulate the request path by encoding backslashes and dot‑segments, thereby bypassing the proxy prefix validation. The attacker can access files or resources located outside the intended prefix on the upstream server. The impact identified is exclusively a confidentiality exposure, as the attacker gains read access to upstream resources that should be protected.

Affected Systems

Affected products include the @fastify/http-proxy Fastify plugin, specifically versions 11.6.0, 11.6.1, and 11.6.2. The vulnerability has been rectified in version 11.6.3 and later, so any deployments using those releases are no longer impacted.

Risk and Exploitability

The CVSS score of 5.9 indicates moderate severity, and the EPSS score is not available; the vulnerability is not listed in the CISA KEV catalog. Exploitation requires only an unauthenticated HTTP request containing a crafted percent‑encoded path that resolves to a backslash followed by a double‑dot segment on systems that treat backslashes as path separators. The attack vector is remote and does not depend on privileged access, but success relies on the upstream server's path handling behavior. Monitoring for anomalous request patterns and applying the official patch reduces risk.

Generated by OpenCVE AI on November 2, 2026 at 11:24 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade @fastify/http-proxy to version 11.6.3 or later to apply the fix.
  • If immediate upgrade is not possible, add a path validation filter that rejects percent‑encoded backslashes before the request reaches the proxy.
  • Verify that your upstream server does not interpret backslashes as path separators; if it does, reconfigure the upstream or add reverse‑proxy logic to normalize paths.

Generated by OpenCVE AI on November 2, 2026 at 11:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 02 Nov 2026 10:30:00 +0000

Type Values Removed Values Added
Description @fastify/http-proxy is a Fastify plugin that proxies HTTP requests to an upstream server under a configured prefix. In versions 11.6.0 through 11.6.2, the destination validation normalizes literal backslashes before it percent-decodes the request path, so a path that encodes its backslashes and dot-segments survives the dot-segment check and is only turned into backslash and double-dot sequences after that check has passed. When the upstream resolves on a platform that treats a backslash as a path separator, the forwarded request walks out of the configured proxy prefix and reaches a sibling location on the upstream. An unauthenticated remote attacker can use this to retrieve upstream resources outside the intended prefix, so the impact is confidentiality only, and exploitation depends on the upstream's path handling. The issue is fixed in @fastify/http-proxy 11.6.3, and users should upgrade to 11.6.3 or later. This is a follow-up to the earlier prefix-escape fix, which did not account for the encoded-backslash form.
Title @fastify/http-proxy vulnerable to prefix escape via percent-encoded backslash dot-segments
Weaknesses CWE-22
References
Metrics cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: openjs

Published:

Updated: 2026-11-02T10:07:08.695Z

Reserved: 2026-10-31T14:04:08.530Z

Link: CVE-2026-120214

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-02T11:17:31.277

Modified: 2026-11-02T11:17:31.277

Link: CVE-2026-120214

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-02T11:30:14Z

Weaknesses
  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')