Skip to main content
Menu
CVEs

Fastify HTTP Proxy path traversal past prefix checks via semicolon segments

CVE-2026-127060EUVD-2026-130504Published November 19, 2026, updated

6.5MediumCNA
Exploited
No known exploitation
Fix
Fixed in 11.6.10
Who is exposed
Not reported

Summary

The @fastify/http-proxy plugin has a flaw that lets a remote attacker, without logging in, send a request whose path uses a semicolon path parameter in a parent-directory segment, which slips past the proxy's path checks. This lets the attacker escape the path prefix the proxy is meant to expose and reach content above the intended subtree on the upstream server, and on some servlet containers, cross into other application contexts.

Written by a model

Original description

@fastify/http-proxy is a Fastify plugin that proxies HTTP and WebSocket traffic to an upstream server. In versions before 11.6.10, it rejects destinations containing 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 check, and the WHATWG URL parser keeps it as an ordinary segment so the rewrite-prefix containment check also passes. Servlet containers such as Apache Tomcat and Jetty strip semicolon path parameters from each segment before resolving dot-segments, so a request routed through the configured prefix is rewritten and reaches the upstream where it resolves above the intended subtree, escaping the path the proxy is meant to expose and, on some containers, crossing application contexts. Both the HTTP and WebSocket proxy paths are affected. The issue is fixed in @fastify/http-proxy 11.6.10, and users should upgrade to 11.6.10 or later.

What to do

Upgrade to a fixed version: 11.6.10.

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-127060 (@fastify/http-proxy vulnerable to prefix escape 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-127060 (entry last updated 2026-11-19):
Affected:
- npm package @fastify/http-proxy: fixed in 11.6.10
Fixed versions: 11.6.10.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-127060 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-127060 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-http-proxy/security/advisories/GHSA-7mjf-mp6r-87p8
- 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-127060
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-127060"}.

Affected versions

cve.now Index

36Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach12/20@fastify/http-proxy: 549.5K downloads a week
  • Severity6.5/10CVSS 6.5
  • No patch0/5No signal

What would change the score

  • Would score about 81 if added to CISA KEV
  • Would score about 76 if CISA's SSVC rates exploitation active
  • Would score about 41 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-http-proxy · Advisory GHSA-7mjf-mp6r-87p8
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-127060
RecordNVD · CVE-2026-127060
Other links 1
Linkcna.openjsf.org · security-advisories.html

Questions about CVE-2026-127060

Is CVE-2026-127060 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

Which versions are affected by CVE-2026-127060?

@fastify/http-proxy (npm): before 11.6.10.

Source: cve.now feed data

How do I fix CVE-2026-127060?

Upgrade to a fixed version: 11.6.10.

Source: cve.now feed data

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