CVE-2026-133212: Fastify Plugin Smuggling Flaw

A critical flaw in a popular Fastify plugin could let an attacker smuggle unauthorised requests into the servers behind a web application. Tracked as CVE-2026-133212 and published on 20 November, the vulnerability scores 9.0 out of 10 and affects versions of the @fastify/reply-from plugin before 12.9.1. A fix is available in version 12.9.1, and users are advised to upgrade.
@fastify/reply-from is a plugin for the Fastify web framework that forwards an incoming HTTP request to an upstream server. Developers use it to build proxies and gateways that pass traffic between backend systems, which means it often sits in internet-facing services handling public web traffic. Because it deals with the boundary between one server and the next, a mistake in how it handles requests can be turned against the systems behind it.
How the flaw works
The problem appears when the plugin forwards a request whose body is never 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. In those cases the plugin still forwards the client's Content-Length header while sending no body at all. The upstream server is left waiting for body bytes that never arrive, so it treats the bytes of the following request as the unfinished body of the first one. That confusion over where one request ends and the next begins is known as HTTP request smuggling, recorded as CWE-444.
An attacker who can send requests through an affected proxy can use that desynchronisation to inject their own requests into the stream, potentially reaching parts of the upstream service they should not be able to reach. No login is needed, and no user interaction is required. The CVSS vector records the attack complexity as high, which means the attack is not trivial to carry out, but the impact is rated high across confidentiality, integrity and availability, and the scope is changed, meaning the damage can extend beyond the vulnerable component itself.
Who is affected
Any application using @fastify/reply-from in a version before 12.9.1 is affected, wherever the plugin is used to forward requests. The risk is greatest for services exposed to the public internet, since anyone on the network can send the crafted requests, but internal services are not automatically safe if they accept requests from other systems or untrusted internal actors. The flaw is not listed in the US CISA catalogue of vulnerabilities known to be exploited, and no in-the-wild exploitation has been reported.
What to do now
The fix is straightforward: upgrade @fastify/reply-from to version 12.9.1 or later. Teams should start by inventorying their applications to find every place the plugin is used, then check whether those services are reachable from the public internet and prioritise the exposed ones. After upgrading, it is worth confirming the new version is actually the one loaded by each running deployment, since a version bump in a manifest does not help if an older build is still serving traffic.