External risk intelligence

Fabio Router Path Traversal Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-104099

Fabio is an HTTP(S) and TCP router designed specifically to act as an edge gateway or proxy for services. As a load balancer and routing layer, it is typically deployed at the network edge to handle incoming traffic, making it a public-facing service by design in common deployment patterns.

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

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

Fabio, a router for applications managed by Consul, has a vulnerability that could allow unauthenticated access to protected resources by manipulating URL paths. This issue affects Fabio versions prior to 1.7.3 and could lead to unauthorized data exposure or modification if a less restrictive fallback route exists.

  • Unauthenticated access to protected resources.
  • Affects edge routing and service protection.
  • Confirm if Fabio is used and check for fallback routes.

Attack Path

How an attacker could exploit the issue

An attacker can target Fabio, an HTTP(S) and TCP router, by sending specially crafted requests. These requests can bypass access controls by exploiting how Fabio processes URL paths, allowing access to protected resources. This bypass leads to unauthorized access to sensitive information and the ability to modify data.

  • Network access is required.
  • Requests with altered URL paths trigger the vulnerability.
  • Bypasses access controls and exposes resources.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an attacker to bypass access controls configured in Fabio. When specific path manipulation techniques are used, requests may reach backend services with less restrictive routing, potentially serving protected resources without proper authentication or authorization.

  • Protected resources could be exposed.
  • Path manipulation may bypass access controls.
  • Unauthorized access to sensitive data.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Fabio router's vulnerability requires coordinated action between application owners and infrastructure or platform teams responsible for its deployment. The immediate priority is to ascertain the presence and exposure of Fabio instances within your environment. Subsequently, confirm if these instances are business-critical and identify the accountable teams for each. Planning remediation will then depend on the assessed risk and operational capacity.

  • Application and Infrastructure teams own resolution.
  • Verify Fabio's reachability and business impact.
  • Plan remediation based on identified 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 Fabio and how is it used?

Fabio is an open-source HTTP and TCP router designed to handle traffic for applications managed by Consul. It acts as a load balancer or edge gateway, dynamically routing incoming requests to appropriate services based on the registry, making it a critical component for managing service communication and enforcing access controls at the network edge.

What does CWE-289 mean for CVE-2026-104099?

This vulnerability involves Improper Validation of URL paths. In Fabio, the router selects a target based on the raw path, but it may misinterpret complex paths containing dot-segments or repeated slashes. This weakness allows a request to bypass intended security checks and reach a backend service that treats the normalized path as a valid, unrestricted request, effectively ignoring the configured authorization policies.

How do requests trigger this vulnerability?

An attacker triggers this by submitting requests with manipulated URL paths, such as those using encoded dots or redundant slashes, that disguise the true destination. This does not trigger the bug if the Fabio instance lacks a less restrictive fallback route that maps to the same backend; without such a path, the system simply returns a 404 error instead of exposing the protected resource.

Is my environment at risk from this Fabio issue?

Halo Surface Signal indicates that because Fabio is typically deployed as an edge gateway to handle external traffic, it is very likely to be public-facing by design. You should care if your Fabio instance is reachable from the internet or sits in a position where untrusted requests can reach backend applications that rely on Fabio for authentication and authorization enforcement.

How do I respond to CVE-2026-104099?

The primary response is to update Fabio to version 1.7.3 or later. Before updating, coordinate with your infrastructure and application teams to locate all active Fabio instances, determine which are business-critical, and assess whether those instances utilize fallback routes that could be exploited to bypass your existing security controls.

References