Description
@fastify/reply-from is a Fastify plugin that forwards requests to an upstream HTTP server. In versions up to and including 12.8.0, the plugin validated proxy paths against forward-slash dot-segments only and then built the target with the WHATWG URL parser, which normalizes a backslash and its percent-encoded form to a forward slash on the http, https, ws, and wss schemes. A path that uses backslash dot-segments therefore bypasses the traversal check and resolves to a different upstream path, so an application that scopes proxying to an upstream prefix, or relies on route guards in front of the forwarding call, can have an unauthenticated request escape the intended prefix and reach other upstream endpoints. The resulting access to unintended upstream resources is primarily a confidentiality impact with limited integrity impact. The issue is fixed in @fastify/reply-from 12.8.1, where the path is normalized and any segment resolving to a single or double dot, along with control characters and ambiguous whitespace, is rejected before the URL is constructed, and users should upgrade to 12.8.1 or later. There is no workaround other than upgrading.
Published: 2026-11-02
Score: 8.2 High
EPSS: n/a
KEV: No
Impact: Unauthenticated path traversal enabling unintended upstream access with a confidentiality impact
Action: Upgrade immediately
AI Analysis

Impact

The vulnerability arises when the plugin processes request paths containing backslash dot-segments. The path is normalized by the URL parser, converting backslashes to forward slashes and thereby bypassing the intended prefix check. As a result, an attacker can craft a request that reaches an upstream endpoint outside the scoped prefix, exposing information that should remain confidential. The flaw does not alter data, so integrity impact is limited.

Affected Systems

All installations of the @fastify/reply-from plugin with versions up to and including 12.8.0 are affected. The issue applies to Node.js applications using Fastify that forward requests with this plugin.

Risk and Exploitability

The CVSS score of 8.2 indicates a high severity. The EPSS score is not available, and the vulnerability is not listed in CISA’s KEV catalog. An attacker with network access to the application can exploit the flaw by sending a crafted URL path containing backslash dot-segments. The compromised path will be resolved to an unintended upstream endpoint, granting the attacker access to privileged resources without authentication.

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

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade @fastify/reply-from to version 12.8.1 or later.
  • Reconfigure proxy path validation to enforce strict prefix checks and avoid reliance on the plugin alone.
  • Review application routes to ensure that unauthenticated requests cannot reach forwarding endpoints; add route guards or authentication as needed.

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

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

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

Type Values Removed Values Added
Description @fastify/reply-from is a Fastify plugin that forwards requests to an upstream HTTP server. In versions up to and including 12.8.0, the plugin validated proxy paths against forward-slash dot-segments only and then built the target with the WHATWG URL parser, which normalizes a backslash and its percent-encoded form to a forward slash on the http, https, ws, and wss schemes. A path that uses backslash dot-segments therefore bypasses the traversal check and resolves to a different upstream path, so an application that scopes proxying to an upstream prefix, or relies on route guards in front of the forwarding call, can have an unauthenticated request escape the intended prefix and reach other upstream endpoints. The resulting access to unintended upstream resources is primarily a confidentiality impact with limited integrity impact. The issue is fixed in @fastify/reply-from 12.8.1, where the path is normalized and any segment resolving to a single or double dot, along with control characters and ambiguous whitespace, is rejected before the URL is constructed, and users should upgrade to 12.8.1 or later. There is no workaround other than upgrading.
Title @fastify/reply-from vulnerable to path traversal via backslash dot-segment prefix escape
Weaknesses CWE-22
References
Metrics cvssV3_1

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


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: openjs

Published:

Updated: 2026-11-02T10:39:22.468Z

Reserved: 2026-10-27T09:25:28.170Z

Link: CVE-2026-117518

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

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

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

Link: CVE-2026-117518

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')