cve.bz

CVE-2026-104099 Fabio: Access-control bypass through unnormalized request paths

9.1 criticalEPSS 0.6%Fix available

Critical (9.1) in fabiolb fabio. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/fabiolb/fabio 1.7.3.

On this page
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.

Severity

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.6% estimated probability of exploitation activity in the next 30 days; 48th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-11-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-41 Improper Resolution of Path Equivalence
CWE-289 Authentication Bypass by Alternate Name
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control, A07:2025 Authentication Failures
Published
Modified
Assigned by
GitHub_M (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • github.com/fabiolb/fabio (Go): fixed in 1.7.3

Ask an AI about this CVE

Show the promptExplain CVE-2026-104099 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-104099?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-104099?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-104099 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
fabiolb fabio< 1.7.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-4hrh-34w3-5ww8Gogithub.com/fabiolb/fabio<1.7.31.7.3

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

Attack patterns (CAPEC)

  • CAPEC-3 Using Leading 'Ghost' Character Sequences to Bypass Input Filters Likelihood: Medium · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON