External risk intelligence

@fastify/express Path Traversal and Middleware Bypass

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-133120

The vulnerability affects a web framework middleware component used to handle incoming HTTP requests. Because this component is designed to facilitate web application routing and middleware processing, it is typically deployed in public-facing web services and API endpoints that are directly reachable from the internet.

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

The @fastify/express compatibility layer may allow unauthenticated attackers to bypass security middleware, potentially exposing protected routes and data by exploiting differences in how URLs are processed.

  • Security bypass in web framework middleware.
  • Affects public-facing web services and APIs.
  • Confirm relevance and assess exposure.

Attack Path

How an attacker could exploit the issue

An attacker could bypass security checks by sending specially crafted requests to a web application using the @fastify/express compatibility layer. By exploiting how the application processes encoded URLs or specific request formats, an attacker could trick the system into skipping middleware designed to protect routes, potentially allowing unauthorized access to sensitive handlers.

  • No authentication required for access.
  • Special request formats bypass middleware.
  • Risk of unauthorized access to protected routes.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, an unauthenticated client could bypass intended security middleware, potentially reaching route handlers that should be protected by authentication, authorization, or rate-limiting mechanisms. This could affect service behavior by allowing unintended access to functionalities or data.

  • Protected route handlers.
  • Bypassing security middleware.
  • Unauthorized access to functionalities.

Operational Fix

Recommended remediation, mitigation, and detection steps

Platform and application teams are most likely responsible for addressing this vulnerability, as it affects a compatibility layer for web frameworks used in request handling. The first practical step is to identify all instances of the affected technology, confirm their reachability and business criticality, and then identify the accountable owner to plan remediation based on assessed risk.

  • Platform/Application owners should address this.
  • Verify affected instances and their criticality.
  • Plan phased remediation by risk.

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 @fastify/express?

It is a compatibility tool that enables developers to use existing Express.js middleware within a Fastify web application. It acts as an integration layer, allowing teams to leverage the large Express ecosystem while building services on the high-performance Fastify framework.

What does CVE-2026-133120 mean for my application?

This vulnerability involves inconsistent interpretation of request paths, categorized as CWE-174 and CWE-436. When the compatibility layer and Fastify disagree on the request URL, security middleware—such as authentication or rate-limiting guards—may be completely skipped. This allows unauthorized requests to reach sensitive route handlers that should have been protected.

How can an attacker trigger this vulnerability?

An attacker triggers this by sending specially formatted HTTP requests that confuse path processing. Examples include requests using backslashes, double-encoded percent signs, or targets starting with an asterisk. Note that this bug relies on these specific malformed request patterns; standard, correctly formatted requests do not trigger the bypass.

Is my application at risk if it uses this component?

According to Halo Surface Signal, this component is designed for routing and middleware, meaning it is often found in public-facing services. If your application handles internet traffic directly, it is highly likely to be exposed. You should prioritize assessment if this technology powers your public-facing web services or API endpoints.

What should I do to secure my environment?

Your first step is to locate all applications using @fastify/express and determine which are reachable by users. Once identified, work with the application owners to update the library to version 4.0.10 or later, which contains the fix for these path-processing inconsistencies.

References