Answer in brief
CVE-2026-133212 records a Critical severity (CVSS 9.0) vulnerability in @fastify/reply-from vulnerable to request smuggling via an unsatisfied forwarded Content-Length. The current sources do not mark it as known exploited. The current feed maps @fastify/reply-from/@fastify/reply-from (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps @fastify/reply-from/@fastify/reply-from (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| @fastify/reply-from/@fastify/reply-fromgeneric | >=0 <12.9.1 | 12.9.1 |
Published upstream
Nov 20, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 20, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 20, 2026
@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.
Quoted source text, attributed separately from HOL analysis.