CVE-2026-127060: @fastify/http-proxy · Path Traversal
Affects @fastify/http-proxySource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 11.6.10 when convenient.
Data as of 19 Nov 2026, 18:37 UTC
Thin evidence
One scorer or none| CNA (openjs) | CVSS 3.1 | 6.5 |
|---|
- Patch
- Available – fixed in 11.6.10
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade @fastify/http-proxy to 11.6.10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| @fastify/http-proxy@fastify/http-proxy | Affected
| Fixed in
|
npm@fastify/http-proxypkg:npm/@fastify/http-proxyOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to @fastify/http-proxy version 11.6.10 or later, where this path traversal vulnerability is fixed. No other mitigation is required as the fix addresses the root cause.
Description
@fastify/http-proxy versions before 11.6.10 contain a path traversal vulnerability (CWE-22) due to improper handling of semicolon path parameters in destination URLs. This allows crafted requests to bypass directory restrictions and access resources outside the intended proxy subtree, affecting both HTTP and WebSocket proxy paths. The issue is fixed in version 11.6.10.