# CVE-2026-133212: @fastify/reply-from vulnerable to request smuggling via an unsatisfied forwarded Content-Length


- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Nov 2026
- **Updated:** 20 Nov 2026

## What is CVE-2026-133212?

CVE-2026-133212 is a critical vulnerability in @fastify/reply-from, published on 20 Nov 2026. 

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

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

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

1 open source package ship an affected version, including %40fastify/reply-from.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `%40fastify/reply-from` | npm | `pkg:npm/%40fastify/reply-from` | All versions | 12.9.1 |

## How do I fix CVE-2026-133212?

Upgrade each affected package to the fixed version listed for it above. Each package has its own fixed versions.

## Is CVE-2026-133212 being exploited?

There is no known exploitation of CVE-2026-133212 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-133212 and fix it if it is affected.

What it is: CVE-2026-133212 is a critical vulnerability in @fastify/reply-from, published on 20 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-133212 in the wild and no public exploit code.

Affected packages and fixed versions:
- %40fastify/reply-from (npm): affected all versions; fixed in 12.9.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-133212/ (Markdown: https://insights.sbomify.com/CVE-2026-133212/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-133212
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-133212
- OSV: https://osv.dev/vulnerability/CVE-2026-133212

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-133212/
Summaries are generated and may contain mistakes; the official description above is the record.
