Fabio
Fabio: Access-control bypass through unnormalized request paths
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.7.3
Fixed in 1.7.3
Mitigation
Upgrade fabio to 1.7.3 or later.
References
- Vendor advisory github.com/fabiolb/fabio/security/advisories/G…
- Patch github.com/fabiolb/fabio/commit/f00ce1a446a4b7…
- Release notes github.com/fabiolb/fabio/releases/tag/v1.7.3
1 more
- Release notes github.com/fabiolb/fabio/releases/tag/v1.8.0
Timeline
Days relative to CVE publicationFirst public PoC 1.4 days after publication; not in CISA KEV. First PoC: LLCForge/CVE-2026-104099 (created 21 Nov 2026, found by us: 21 Nov 2026).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| LLCForge/CVE-2026-104099 | 21 Nov 2026 +1.4 d | 21 Nov 2026 | 0 | PoC
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.