Skip to main content
VulnerabilityPublished

CVE-2026-130886: @fastify/reply-from · Path Traversal

Affects @fastify/reply-fromSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 12.8.4 soon.

Data as of 19 Nov 2026, 18:35 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (openjs)CVSS 3.18.2
Patch
Available – fixed in 12.8.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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/reply-from to 12.8.4.

Affected software

ProductAffectedFixed in
@fastify/reply-from@fastify/reply-fromAffected
  • >=12.8.1 <12.8.4
Fixed in
  • 12.8.4
npm@fastify/reply-frompkg:npm/@fastify/reply-fromOther threatsAffected
  • >=12.8.1 <12.8.4
Fixed in
  • 12.8.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade @fastify/reply-from to version 12.8.4 or later, where this path traversal vulnerability is fixed. No other mitigation is required as the fix addresses the root cause.

Description

@fastify/reply-from versions 12.8.1 through 12.8.3 contain a path traversal vulnerability in the buildURL function. This occurs because the function's check for parent-directory segments can be bypassed when the source URL begins with the same scheme as the base (e.g., http or https). An attacker can craft a payload that uses a percent-encoded parent-directory sequence glued to the scheme, which passes the check but results in forwarding a path outside the intended upstream prefix. This allows unauthenticated clients to escape route guards and access unauthorized upstream endpoints. The issue is fixed in version 12.8.4.

References

Community reviews

Loading reviews…