External risk intelligence

Attacker can bypass security checks on Fastify web applications.

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-33804

A security flaw in @fastify/middie lets attackers bypass checks on Fastify apps if a specific old setting is active, potentially exposing sensitive data.

4Halo Surface Signal

Fastify\/middie

before 9.3.2

External exposure likelihood

Halo Surface Signal score for CVE-2026-33804

The vulnerability affects middleware within the Fastify web framework. Applications using this framework are commonly deployed as internet-facing web applications or APIs. Because the middleware component sits directly in the path of incoming web requests, it is inherently exposed to the network in standard web application deployments.

Horizon Alert

Summary of the vulnerability and why it matters

A middleware bypass vulnerability in @fastify/middie could allow unauthenticated requests to reach sensitive application logic. This occurs when a deprecated Fastify option is enabled, causing the router to incorrectly handle paths with duplicate slashes. Attention is warranted because unpatched systems could have their authentication and authorization checks bypassed.

  • Bypass allows unauthorized access.
  • Affects internet-facing applications.
  • Potentially critical security flaw.

Attack Path

How an attacker could exploit the issue

An attacker can bypass middleware controls by sending specially crafted requests with duplicate slashes to a Fastify application that has the deprecated `ignoreDuplicateSlashes` option enabled. This allows them to access or manipulate resources that should be protected by the bypassed middleware.

  • Network access required.
  • Malformed URL targets middleware.
  • Deprecated option must be enabled.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability allows attackers to bypass middleware for authentication and authorization by exploiting duplicate slash handling in Fastify, but only when a deprecated option is enabled. The limited scope of exploitation due to the deprecated feature may reduce immediate weaponization, although the critical impact remains.

  • Affects deprecated feature.
  • No observed exploitation signals.
  • Recency signal weak.

Priority actions

Operational Fix

Recommended remediation, mitigation, and detection steps

Prioritize upgrading `@fastify/middie` to version 9.3.2 to address the middleware bypass vulnerability, as this is the direct fix. If immediate patching is not feasible, consider disabling the deprecated `ignoreDuplicateSlashes` option in Fastify to mitigate the risk.

  • Upgrade @fastify/middie to 9.3.2.
  • Disable `ignoreDuplicateSlashes` option.
  • Monitor for bypassed traffic.

Frequently asked questions

What is the vulnerability in @fastify/middie versions 9.3.1 and earlier?

@fastify/middie versions 9.3.1 and earlier are vulnerable to a middleware bypass. This occurs when the deprecated Fastify `ignoreDuplicateSlashes` option is enabled, causing the middleware path matching logic to not account for duplicate slash normalization by Fastify's router. This allows requests with duplicate slashes to bypass middleware authentication and authorization checks.

How can an attacker exploit the @fastify/middie vulnerability?

An attacker can exploit this vulnerability by sending specially crafted requests containing duplicate slashes to a Fastify application that has the deprecated `ignoreDuplicateSlashes` option enabled. This bypasses the middleware's security controls, potentially allowing unauthorized access to resources.

What is the weakness class for CVE-2026-33804 and how does it affect applications?

The weakness class for CVE-2026-33804 is CWE-436, which relates to interpretation errors in the code. In this case, it allows for middleware bypass by exploiting how duplicate slashes in URLs are handled, potentially leading to unauthorized access and manipulation of protected resources.

What is the relevance of the @fastify/middie vulnerability, and what threat advisory is associated with it?

This vulnerability is relevant because it affects internet-facing applications using the Fastify web framework, allowing unauthenticated requests to bypass security checks. The Halo Surface Signal indicates a 'Likely' threat due to the common deployment of Fastify in network-exposed scenarios.

How can the @fastify/middie vulnerability be practically responded to?

To address this vulnerability, upgrade `@fastify/middie` to version 9.3.2. If an immediate upgrade is not possible, disable the deprecated `ignoreDuplicateSlashes` option in Fastify. Monitoring traffic for signs of bypassed access is also recommended.

References