
Cloud Vulnerability DB
A community-led vulnerabilities database
CVE-2026-133212 is an HTTP Request Smuggling vulnerability in the @fastify/reply-from Fastify plugin, which forwards incoming HTTP requests to upstream servers. In versions before 12.9.1, the plugin incorrectly forwards the client's Content-Length header to the upstream even when no body is written (e.g., for GET, HEAD, or TRACE requests with a body, or requests with falsy JSON bodies such as null, 0, false, or ""). This desynchronizes the upstream connection, allowing an attacker to smuggle arbitrary HTTP requests. The vulnerability was disclosed and patched on November 20, 2026, with a CVSS v3.1 base score of 9.0 (Critical) (GitHub Advisory).
The root cause is classified as CWE-444 (Inconsistent Interpretation of HTTP Requests / HTTP Request Smuggling). When @fastify/reply-from proxies a request that carries no body (or a falsy JSON body), it still forwards the original Content-Length header to the upstream server without sending any body bytes. On the core Node.js http transport (when undici: false is set, or in releases before 5.0.0 where it was the default), the keep-alive socket is returned to the pool still "owing" those bytes. The upstream server then interprets the leading bytes of the next request on that socket as the remainder of the previous request's body, enabling classic CL.0-style HTTP request smuggling. The default undici transport and HTTP/2 paths are not affected by this issue (GitHub Advisory).
A successful exploit allows an unauthenticated attacker to have arbitrary HTTP requests executed by the upstream server outside the proxy's routes, hooks, and authentication controls. This can expose upstream-only endpoints and their responses (confidentiality breach), allow unauthorized actions on the upstream (integrity breach), and exhaust the upstream connection pool by holding connections open until timeout (availability breach). The changed scope means the impact extends beyond the proxy itself to backend systems that would otherwise be protected (GitHub Advisory).
No public proof-of-concept exploit code or in-the-wild exploitation has been reported as of the disclosure date. The EPSS score is 0.0, and the NVD SSVC assessment indicates no known exploitation (GitHub Advisory). The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation requires high attack complexity (precise timing and byte-length matching), but no authentication or user interaction is needed, making it a realistic threat in targeted scenarios against deployments using the legacy Node.js http transport.
@fastify/reply-from versions before 12.9.1 with the legacy Node.js http transport enabled (undici: false or pre-5.0.0 default).Content-Length header to match the exact byte length of the intended smuggled request.Content-Length to the upstream but sends no body. The upstream's keep-alive socket is returned to the pool still expecting those bytes.Content-Length headers arriving at the Fastify proxy.Upgrade @fastify/reply-from to version 12.9.1 or later, which fixes the issue by forwarding any parsed body regardless of its truthiness and resetting an inherited Content-Length to 0 when no body is written (GitHub Advisory). If an immediate upgrade is not possible, two workarounds are available: (1) use the default undici transport (do not set http option or undici: false), which is not affected; or (2) add an onRequest hook that runs before reply.from() to reject requests carrying a body on methods that should not have one (GET, HEAD, TRACE) and to avoid forwarding falsy JSON bodies.
Fix availability across major Linux distributions and their releases.
Source: This report was generated using AI
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."