External risk intelligence

@fastify/reply-from Request Smuggling Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.0)

CVE-2026-133212

The vulnerability affects a Fastify plugin used to forward HTTP requests to upstream servers. As a component designed for proxying, gateway functionality, or request handling in web applications, it is commonly deployed in internet-facing services that handle public HTTP traffic, making it a likely component of an externally reachable web infrastructure.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A security vulnerability has been identified in a Fastify plugin that forwards HTTP requests. This issue could potentially allow an attacker to manipulate requests sent to upstream servers, leading to a desynchronization of connections. The main concern is to confirm if this specific plugin is in use within our environment and if so, to what extent.

  • Plugin forwards requests, creating potential connection risks.
  • Affects how web requests are proxied to other servers.
  • Confirm usage and assess exposure to upstream risks.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending a specially crafted request to a server using the affected Fastify plugin. This request, which might carry a `Content-Length` header but no actual body, can trick the upstream server into misinterpreting subsequent requests. This desynchronization allows the attacker to inject malicious requests, potentially leading to significant compromise.

  • Unauthenticated network access required.
  • Triggered by a request with a falsy body.
  • Allows request smuggling and desynchronization.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an attacker to desynchronize a connection and smuggle a request to an upstream server when the @fastify/reply-from plugin forwards certain types of requests without a body but with a Content-Length header. This could affect the integrity and availability of the upstream service.

  • Upstream server requests.
  • Request header manipulation.
  • Service integrity and availability.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in `@fastify/reply-from` impacts teams responsible for managing web application infrastructure, particularly those utilizing Fastify for request forwarding. The first step for these teams is to inventory all instances of the affected plugin, assess their exposure to external traffic, and confirm business criticality to prioritize remediation efforts by identifying the accountable application or platform owner.

  • Own by application or platform teams.
  • Verify external reachability and criticality.
  • Plan and coordinate upgrades.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the @fastify/reply-from plugin used for?

This component is a plugin for the Fastify web framework designed to forward incoming HTTP requests to an upstream server. It acts as a bridge in web architectures, enabling proxying or gateway functionality where one server passes traffic along to another. Developers commonly use it when building services that need to route requests between different backend systems or microservices.

What does CVE-2026-133212 mean in plain English?

This vulnerability is classified as CWE-444, or HTTP Request Smuggling. It occurs when a proxy server and an upstream server disagree on where one request ends and the next begins. By sending specific requests that contain misleading header information, an attacker can confuse the upstream server into misinterpreting the boundaries of subsequent data, essentially allowing them to smuggle unauthorized requests into the server's processing stream.

How is this request smuggling vulnerability triggered?

The issue is triggered when the plugin forwards a request that includes a Content-Length header but lacks an actual body, such as certain GET or TRACE requests, or those with a falsy JSON body. It does not trigger when the request body is properly transmitted, as the bug relies on the upstream server waiting for data that was never sent, leading it to mistakenly incorporate the next legitimate request as part of the previous one.

Why should I care about this if my app is internal?

According to Halo Surface Signal, this plugin is often used in infrastructure that handles public HTTP traffic, making it a likely component of internet-facing services. While internal services are theoretically at lower risk of direct exploitation from the public internet, they may still be vulnerable if they accept requests from other compromised systems or untrusted internal actors that can reach the proxy.

Do I need to update my software to fix this?

Yes. The vulnerability is resolved in version 12.9.1 of @fastify/reply-from. Your first step should be to inventory your applications to identify which ones rely on this specific plugin. Once identified, coordinate with your development or platform teams to prioritize upgrading to version 12.9.1 or later to ensure the plugin correctly handles request body and header forwarding.

References