Skip to main content
Menu
CVEs

Fastify Reply From path traversal in request forwarding

Only affects @fastify/reply-from 12.8.1 through 12.8.3 when the application scopes proxying to an upstream prefix or the upstream percent-decodes request paths. Fixed in 12.8.4.

CVE-2026-130886EUVD-2026-130500Published November 19, 2026, updated

8.2HighCNA
Exploited
No known exploitation
Fix
Fixed in 12.8.4
Who is exposed
Not reported

Summary

A path traversal flaw in the @fastify/reply-from plugin lets a remote, unauthenticated attacker send a request with a scheme-prefixed, percent-encoded parent-directory sequence that passes the plugin's check and is forwarded unchanged. If the upstream server decodes the path before resolving it, the attacker can escape the configured prefix and reach sibling or parent endpoints.

Written by a model

Original description

@fastify/reply-from is a Fastify plugin that forwards requests to an upstream HTTP server. In versions 12.8.1 through 12.8.3, its buildURL function checked the attacker-supplied source string for parent-directory segments, but when the source begins with the same special scheme as the base, such as http or https, the WHATWG URL parser drops the scheme and resolves the remainder as a relative path. A payload that glues the scheme to a percent-encoded parent-directory sequence therefore passes the check, because the inspected segment reads as the scheme plus the dots rather than a bare parent-directory token, while the proxy forwards the encoded traversal unchanged. An upstream that percent-decodes the request path before resolving dot-segments then serves a path outside the configured prefix, so an unauthenticated client scoped to an upstream prefix, or relying on Fastify route guards in front of the proxy, can escape that prefix and reach sibling or parent upstream endpoints. The per-segment check added in 12.8.1 is what the scheme prefix bypasses, and releases up to 12.8.0 already rejected the decoded form. The issue is fixed in @fastify/reply-from 12.8.4, and users should upgrade to 12.8.4 or later.

Who should check

Teams running @fastify/reply-from 12.8.1 through 12.8.3 that proxy to upstream prefixes or rely on Fastify route guards in front of reply.from().

“Releases 12.8.1 through 12.8.3 are affected”

github.com

What to do

Upgrade to a fixed version: 12.8.4.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130886 (@fastify/reply-from vulnerable to path traversal via scheme-prefixed encoded dot-segments), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130886 (entry last updated 2026-11-19):
Affected:
- npm package @fastify/reply-from: from 12.8.1, fixed in 12.8.4
Fixed versions: 12.8.4.
Conditions (all must be true for the bug to be hit):
- Affected releases are @fastify/reply-from 12.8.1 through 12.8.3. (source: https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-2ccw-8rvh-6cmg)
- The request source must begin with the same special scheme as the base URL (http or https). (source: https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-2ccw-8rvh-6cmg)
- The application scopes proxying to an upstream prefix, or relies on Fastify route guards in front of reply.from(). (source: https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-2ccw-8rvh-6cmg)
- The upstream percent-decodes the request path before resolving dot-segments. (source: https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-2ccw-8rvh-6cmg)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130886 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130886 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-2ccw-8rvh-6cmg
- https://cna.openjsf.org/security-advisories.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130886
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130886"}.

Affected versions

cve.now Index

37Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach12/20@fastify/reply-from: 733.9K downloads a week
  • Severity8.2/10CVSS 8.2
  • No patch0/5No signal

What would change the score

  • Would score about 82 if added to CISA KEV
  • Would score about 77 if CISA's SSVC rates exploitation active
  • Would score about 42 if advisories confirm default setups are exposed

Impact

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · fastify/fastify-reply-from · Advisory GHSA-2ccw-8rvh-6cmg
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130886
RecordNVD · CVE-2026-130886
Other links 1
Linkcna.openjsf.org · security-advisories.html

Questions about CVE-2026-130886

Is CVE-2026-130886 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A request source that begins with the same http or https scheme as the base URL can use encoded dot-segments to escape the intended upstream prefix. An unauthenticated client can then reach sibling or parent upstream endpoints, which is path traversal.

Source: github.com

Which versions are affected by CVE-2026-130886?

@fastify/reply-from (npm): from 12.8.1 before 12.8.4.

Source: cve.now feed data

Am I affected, and how do I check?

Releases 12.8.1 through 12.8.3 of @fastify/reply-from are affected. The risk depends on setup: the application scopes proxying to an upstream prefix or relies on Fastify route guards in front of reply.from(), and the upstream percent-decodes the request path before resolving dot-segments. Check the installed @fastify/reply-from version in package.json or the lockfile, and review the proxy and upstream configuration.

Source: github.com

How do I fix CVE-2026-130886?

Upgrade @fastify/reply-from to 12.8.4, the fixed version.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.