@fastify/reply-from · @fastify/reply-from · CWE-444 · published 2026-11-20
CVE-2026-133212@fastify/reply-from vulnerable to request smuggling via an unsatisfied forwarded Content-Length
Routine No exploitation evidence; no EPSS score yet.
CVE-2026-133212 is not known to be exploited in the wild. This @fastify/reply-from vulnerability: CVSS 9.0 (v3.1), a successful attack gives total control of the component. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
No fixed version is recorded here yet. Check the vendor advisory linked from the CVE record below.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | — | FIRST EPSS |
| CVSS base score | 9.0 (v3.1)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Weakness: CWE-444: Inconsistent Interpretation of HTTP Requests
Affected versions (from the CVE record)#
- @fastify/reply-from @fastify/reply-from
0to before12.9.1(affected)12.9.1(unaffected)
Description (from the CVE record)#
@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.
Quoted from the CVE Program record.