CVE-2026-133212: critical vulnerability in @fastify/reply-from
@fastify/reply-from vulnerable to request smuggling via an unsatisfied forwarded Content-Length
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
25Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 9
@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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Affected products
@fastify/reply-from · @fastify/reply-fromRelated CVEs — @fastify/reply-from
In the same product, most dangerous first.
CVE-2026-130886HIGH@fastify/reply-from vulnerable to path traversal via scheme-prefixed encoded dot-segmentsEPSS 0.5%CVE-2026-117518HIGH@fastify/reply-from vulnerable to path traversal via backslash dot-segment prefix escapeEPSS 0.5%CVE-2026-33805CRITICAL@fastify/reply-from vulnerable to connection header abuse enabling stripping of proxy-added headersEPSS 0.5%CVE-2026-16158HIGH@fastify/reply-from vulnerable to cross-upstream request routing via URL cache key collisionEPSS 0.4%CVE-2026-127064HIGH@fastify/reply-from vulnerable to path traversal via semicolon path-parameter dot-segmentsEPSS 0.4%CVE-2026-107318HIGH@fastify/reply-from vulnerable to improper certificate validation in built-in HTTPS transportsEPSS 0.1%