Vulnerability DatabaseCVE-2026-133212

CVE-2026-133212: 
JavaScript vulnerability analysis and mitigation

Overview

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).

Technical details

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).

Impact

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).

Exploitability

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.

Exploitation steps

  1. Reconnaissance: Identify a target application using @fastify/reply-from versions before 12.9.1 with the legacy Node.js http transport enabled (undici: false or pre-5.0.0 default).
  2. Craft a smuggling request: Send a GET, HEAD, or TRACE request to the Fastify proxy that includes a body payload. Set the Content-Length header to match the exact byte length of the intended smuggled request.
  3. Trigger the desynchronization: The proxy forwards the Content-Length to the upstream but sends no body. The upstream's keep-alive socket is returned to the pool still expecting those bytes.
  4. Inject the smuggled request: Send a follow-up request on the same connection. The upstream server reads the leading bytes of this new request as the "missing" body of the previous request, effectively prepending attacker-controlled data to the next legitimate request.
  5. Access protected resources: The smuggled request is processed by the upstream outside the proxy's authentication hooks and route guards, potentially reaching internal-only endpoints, reading their responses, or performing unauthorized actions (GitHub Advisory).

Indicators of compromise

  • Network: Unexpected HTTP requests reaching upstream-only endpoints that should not be reachable through the proxy; unusual GET/HEAD/TRACE requests with non-zero Content-Length headers arriving at the Fastify proxy.
  • Logs: Upstream server logs showing requests with malformed or unexpected prefixes on keep-alive connections; requests to internal endpoints with no corresponding proxy access log entry; connection pool exhaustion warnings or timeout errors in the upstream service logs.
  • Process/Application: Elevated rate of upstream connection pool exhaustion events; upstream responses being returned to unexpected clients or sessions; authentication bypass indicators on upstream services (requests processed without expected auth headers set by the proxy).

Mitigation and workarounds

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.

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

RHEL / CentOS

Unknown

Source: This report was generated using AI

Related JavaScript vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-133867CRITICAL9.1
  • JavaScript logoJavaScript
  • @fastify/express
NoYesNov 21, 2026
CVE-2026-133250CRITICAL9.1
  • JavaScript logoJavaScript
  • @fastify/middie
NoYesNov 21, 2026
CVE-2026-133120CRITICAL9.1
  • JavaScript logoJavaScript
  • @fastify/express
NoYesNov 21, 2026
CVE-2026-133312MEDIUM5.3
  • JavaScript logoJavaScript
  • @fastify/rate-limit
NoYesNov 21, 2026
CVE-2026-133273LOW3.7
  • JavaScript logoJavaScript
  • @fastify/swagger-ui
NoYesNov 21, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management