Skip to main content
Menu
CVEs

Fabio access control bypass via unnormalized request paths

Affects Fabio setups where a less restrictive route reaches the same backend as a protected route, in versions before 1.7.3. Fixed in 1.7.3.

CVE-2026-104099Published November 19, 2026, updated

9.1CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 1.7.3
Who is exposed
Not reported

Summary

Fabio, a router for applications managed by Consul, can be tricked into skipping its access controls on protected routes through crafted request paths. A remote attacker without logging in can use dot-segment, encoded-dot, or repeated-slash variants to reach the protected backend resource, but only where a less restrictive fallback route leads to the same backend.

Written by a model

Original description

Fabio is an HTTP(S) and TCP router for deploying applications managed by consul. Prior to 1.7.3, route/table.go selects targets using raw req.URL.Path, while proxy/http_proxy.go applies per-route ACL and basic-auth checks to the selected target and forwards the raw path to the origin. Dot-segment, encoded-dot, or repeated-slash variants can fall through to a less restrictive route that reaches the same backend; the backend then normalizes the path and serves the protected resource without the configured access controls. A less restrictive fallback route must reach the same backend; without one, the request returns 404. This issue is fixed in version 1.7.3.

Who should check

Teams running fabio 1.6.5 or earlier as a Consul-backed router with per-route ACLs or basic auth, where a less restrictive fallback route reaches the same backend.

“github.com/fabiolb/fabio”

github.com

What to do

Upgrade to a fixed version: 1.7.3.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-104099 (Fabio: Access-control bypass through unnormalized request paths), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-104099 (entry last updated 2026-11-19):
Affected:
- fabiolb fabio: fixed in 1.7.3
Fixed versions: 1.7.3.
Conditions (all must be true for the bug to be hit):
- A less restrictive fallback route must reach the same backend as the protected route; without one, the request returns 404. (source: https://github.com/fabiolb/fabio/security/advisories/GHSA-4hrh-34w3-5ww8)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-104099 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-104099 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/fabiolb/fabio/security/advisories/GHSA-4hrh-34w3-5ww8
- https://github.com/fabiolb/fabio/commit/f00ce1a446a4b7a3bccbefbb7bfe4a5e0e3fd817
- https://github.com/fabiolb/fabio/releases/tag/v1.7.3
- https://github.com/fabiolb/fabio/releases/tag/v1.8.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-104099
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-104099"}.

Affected versions

cve.now Index

30Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.1, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 35 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  4. Record last updated
  5. Posted on X by cve.now

Evidence 6

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · fabiolb/fabio · Advisory GHSA-4hrh-34w3-5ww8
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-104099
RecordNVD · CVE-2026-104099
Other links 3
RepositoryGitHub · fabiolb/fabio · Commit f00ce1a4
RepositoryGitHub · fabiolb/fabio · Release v1.7.3
RepositoryGitHub · fabiolb/fabio · Release v1.8.0

Questions about CVE-2026-104099

Is CVE-2026-104099 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A crafted request path that is not normalized can get past a route's per-route IP allow/deny ACL or basic-auth and reach a protected resource such as an admin path. Fabio forwards the request, and the backend normalizes the path and serves the protected resource.

Source: github.com

Which versions are affected by CVE-2026-104099?

fabio: before 1.7.3.

Source: cve.now feed data

Am I affected, and how do I check?

Fabio versions before 1.7.3 are affected, and only where a less restrictive fallback route reaches the same backend as the protected route. Without such a fallback route, the crafted request returns 404. Check the Fabio version and the route configuration to see whether that setup is present.

Source: github.com

How do I fix CVE-2026-104099?

Upgrade Fabio to 1.7.3, which is the fixed version.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.