Fastify Reply From request smuggling in HTTP request forwarding
Affects @fastify/reply-from releases before 12.9.1 that use the core Node.js http transport. Fixed in 12.9.1.
- Exploited
- No known exploitation
- Fix
- Fixed in 12.9.1
- Who is exposed
- Specific setups only
Summary
The @fastify/reply-from plugin, which forwards incoming HTTP requests to an upstream server, can forward a client's Content-Length header without sending the body, such as for a GET or HEAD request that carried one. A remote attacker, without logging in, can use this to desynchronize the connection and smuggle a request to the upstream server.
Written by a model
Original description
@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.
Who should check
Teams running @fastify/reply-from before 12.9.1 that proxy over the core Node.js http transport (http option or undici: false) and forward client requests to upstream servers
“@fastify/reply-from forwards the client's Content-Length to the upstream even when it writes no body”
What to do
Check whether your setup matches what the bug needs.
Uses the core Node.js http transport, set via the http option or undici: false, or a release before 5.0.0 The forwarded request is a GET, HEAD or TRACE carrying a body, or has a falsy JSON bodyUpgrade to a fixed version: 12.9.1.
Workaround: Use the default undici transport (do not set the http option or undici: false)
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133212 (@fastify/reply-from vulnerable to request smuggling via an unsatisfied forwarded Content-Length), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133212 (entry last updated 2026-11-20):
Affected:
- npm package @fastify/reply-from: fixed in 12.9.1
Fixed versions: 12.9.1.
Conditions (all must be true for the bug to be hit):
- Uses the core Node.js http transport, set via the http option or undici: false, or a release before 5.0.0 (source: https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-mx78-9mrq-rfm5)
- The forwarded request is a GET, HEAD or TRACE carrying a body, or has a falsy JSON body (source: https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-mx78-9mrq-rfm5)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, no user action.
Workaround: Use the default undici transport (do not set the http option or undici: false) (source: https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-mx78-9mrq-rfm5)
CISA KEV: CVE-2026-133212 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133212 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-mx78-9mrq-rfm5
- https://cna.openjsf.org/security-advisories.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133212
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133212"}.Affected versions
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach12/20@fastify/reply-from: 733.9K downloads a week
- Severity9/10CVSS 9.0
- No patch0/5No signal
What would change the score
- Would score about 83 if added to CISA KEV
- Would score about 78 if CISA's SSVC rates exploitation active
Impact
- Widely used@fastify/reply-from has 733.9k weekly downloads. npmjs.com
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · fastify/fastify-reply-from · Advisory GHSA-mx78-9mrq-rfm5 |
| CVE record 1Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133212 |
| Other links 1 | |
| Link | cna.openjsf.org · security-advisories.html |
Questions about CVE-2026-133212
Is CVE-2026-133212 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
A client can make the upstream server run arbitrary HTTP requests that bypass the proxy's routes, hooks and authentication. The flaw also lets a client read upstream-only responses and exhaust upstream connection pools.
Source: github.com
Which versions are affected by CVE-2026-133212?
@fastify/reply-from (npm): before 12.9.1.
Source: cve.now feed data
Am I affected, and how do I check?
Releases from 0 up to 12.9.1 are in the affected range. The relevant setup is the core Node.js http transport, selected with the http option or undici: false, or any release before 5.0.0. Check the installed @fastify/reply-from version in the project's package.json or lockfile, and check the http and undici settings where the proxy is registered.
Source: github.com
How do I fix CVE-2026-133212?
Upgrade @fastify/reply-from to 12.9.1. Until the upgrade is applied, use the default undici transport by not setting the http option or undici: false, which the advisory says is not affected.
Source: github.com
Related
- CVE-2026-33805@fastify/reply-from vulnerable to connection header abuse enabling stripping of proxy-added headers
- CVE-2026-130886@fastify/reply-from vulnerable to path traversal via scheme-prefixed encoded dot-segments
- CVE-2026-127064@fastify/reply-from vulnerable to path traversal via semicolon path-parameter dot-segments
- CVE-2025-66415fastify-reply-from bypass of reply forwarding
- CVE-2023-51701@fastify-reply-from JSON Content-Type parsing confusion
- CVE-2026-16158@fastify/reply-from vulnerable to cross-upstream request routing via URL cache key collision
No corrections so far. Something wrong on this page? Report an error.