CVE-2026-133212: @fastify/reply-from · HTTP Request Smuggling
Affects @fastify/reply-fromSource CVE Database V5
Not known to be exploited · CVSS 9.0 Critical : upgrade to 12.9.1 as a priority.
Data as of 20 Nov 2026, 17:59 UTC
Thin evidence
One scorer or none| CNA (openjs) | CVSS 3.1 | 9.0 |
|---|
- Patch
- Available – fixed in 12.9.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 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 20 Nov 2026.
What to do
Upgrade @fastify/reply-from to 12.9.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| @fastify/reply-from@fastify/reply-from | Affected
| Fixed in
|
npm@fastify/reply-frompkg:npm/@fastify/reply-fromOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
@fastify/reply-from is a Fastify plugin that forwards an incoming HTTP request to an upstream server. In versions before 12.9.1, when the plugin forwards a request whose body is not written to the upstream connection, such as a GET, HEAD, or TRACE request that carried a body, or a request with a falsy JSON body, it still forwards the client's Content-Length header while sending no body. The upstream server then treats the bytes of the following request as the unfinished body, which an attacker can use to desynchronize the connection and smuggle a request. The issue is fixed in @fastify/reply-from 12.9.1, and users should upgrade to 12.9.1 or later.