Skip to main content
Menu
CVEs

Fastify Reply From path traversal in HTTP proxy plugin

Only affects @fastify/reply-from before 12.8.4 when it proxies to a Java servlet upstream such as Tomcat, Jetty, WildFly or Spring Boot. Fixed in 12.8.4.

CVE-2026-127064EUVD-2026-130497Published November 19, 2026, updated

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

Summary

The @fastify/reply-from plugin, which forwards requests to an upstream HTTP server, has a path traversal flaw that lets a remote attacker, without logging in, reach internal paths such as admin or internal API endpoints, including with state-changing requests. The attacker sends a path segment with a dot-dot and a semicolon path parameter, which passes the plugin's check and is then resolved as a parent directory by backends such as Apache Tomcat, Jetty, WildFly, and Spring Boot.

Written by a model

Original description

@fastify/reply-from is a Fastify plugin that forwards requests to an upstream HTTP server. In versions before 12.8.4, its buildURL function rejects parent-directory path segments by an exact string match, so a segment that carries a semicolon path parameter, such as a dot-dot segment followed by a semicolon and an optional parameter, is not equal to the plain dot-dot form and passes the traversal check, and the WHATWG URL parser keeps it as an ordinary segment so the base-prefix containment check also passes. Backends that strip semicolon path parameters before resolving dot-segments, such as Apache Tomcat, Jetty, WildFly, and Spring Boot, turn the segment back into a parent-directory reference and resolve it, so an unauthenticated client can escape the intended upstream prefix and reach internal paths such as admin or internal API endpoints, including with state-changing methods. Deployments that proxy to Node.js, nginx, or Express upstreams are not affected. 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 before 12.8.4 that proxy to Java servlet upstreams such as Tomcat, Jetty, WildFly or Spring Boot, especially those scoping proxying to a prefix

“Exploitation requires an upstream that treats ; as a path-parameter delimiter (a Java servlet container)”

github.com

What to do

  1. Upgrade to a fixed version: 12.8.4.

  2. Workaround: Reject requests whose decoded path contains a ; in front of the proxy (for example in an onRequest hook), or configure the servlet upstream to reject path parameters.

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-127064 (@fastify/reply-from vulnerable to path traversal via semicolon path-parameter 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-127064 (entry last updated 2026-11-19):
Affected:
- npm package @fastify/reply-from: fixed in 12.8.4
Fixed versions: 12.8.4.
Conditions (all must be true for the bug to be hit):
- Upstream treats ';' as a path-parameter delimiter (Java servlet container such as Tomcat, Jetty, WildFly or Spring Boot) (source: https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-6mph-mjg3-f943)
- Application scopes proxying to an upstream prefix (source: https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-6mph-mjg3-f943)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
Workaround: Reject requests whose decoded path contains a ; in front of the proxy (for example in an onRequest hook), or configure the servlet upstream to reject path parameters. (source: https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-6mph-mjg3-f943)
CISA KEV: CVE-2026-127064 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-127064 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-6mph-mjg3-f943
- 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-127064
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-127064"}.

Affected versions

cve.now Index

40Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · 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 85 if added to CISA KEV
  • Would score about 80 if CISA's SSVC rates exploitation active
  • Would score about 45 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: yes · Technical impact: partial

  4. Record last updated

Evidence 4

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

Questions about CVE-2026-127064

Is CVE-2026-127064 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 Java servlet upstream can treat a semicolon in a request path as a path-parameter delimiter, so dot-segments after it let unauthenticated requests escape the upstream prefix the proxy was meant to limit. This can reach internal APIs or admin endpoints, including with state-changing methods.

Source: github.com

Which versions are affected by CVE-2026-127064?

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

Source: cve.now feed data

Am I affected, and how do I check?

Versions before 12.8.4 are affected, and only when the application scopes proxying to an upstream prefix and that upstream treats ';' as a path-parameter delimiter, as Tomcat, Jetty, WildFly or Spring Boot do. To check, look at the installed @fastify/reply-from version (for example with npm ls @fastify/reply-from) and confirm what kind of server the upstream is.

Source: github.com

How do I fix CVE-2026-127064?

Upgrade @fastify/reply-from to 12.8.4, which is the listed fixed version. If you cannot upgrade yet, reject requests whose decoded path contains a ';' in front of the proxy, for example in an onRequest hook.

Source: github.com

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