CVE-2026-133212: falha crítica em @fastify/reply-from
@fastify/reply-from vulnerable to request smuggling via an unsatisfied forwarded Content-Length
Publicada em
Aviso por e-mail quando ela entrar no KEV, ganhar PoC pública ou subir de nota.
25Vexday Risk Score
Sem sinal de exploração. Nenhum artefato público de exploração conhecido até agora.
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
Produtos afetados
@fastify/reply-from · @fastify/reply-fromCVEs relacionadas — @fastify/reply-from
No mesmo produto, das mais perigosas para as menos.
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%