Fabio: unauthenticated ACL and basic-auth bypass via unnormalized request paths (CVE-2026-104099)
Severity: critical · Patch status: patched · Since 2026-08-06 · CVE-2026-104099
Fabio, a Go reverse proxy and load balancer, chooses a route from the raw request path, then applies that route's allow/deny and basic-auth checks and forwards the raw path to the backend. A path that is a dot-segment, percent-encoded-dot or double-slash variant of a protected path can match a less restrictive fallback route, skip those checks, and reach the backend, which normalizes the path and serves the protected resource. This needs a fallback route that points to the same backend; without one the request gets a 404. The advisory describes this as the two-tag urlprefix setup that Fabio's access-control documentation tells operators to use. Versions before 1.7.3 are affected, and 1.7.3 is the first patched release. Fabio tagged v1.7.3 on 2026-08-06, months before the advisory was published, so exposed installs had a fix available without an advisory. No exploitation or public proof of concept was found in the sources checked, and the CVE is not on CISA's KEV list. The advisory also notes that gRPC proxy routes never call either access check, so allow= and auth= on proto=grpc routes are silently unenforced.
What to do
- Upgrade Fabio to 1.7.3 or later immediately.
- If upgrade is delayed, normalize or reject dot-segment, encoded-dot, double-slash, and traversal paths at an upstream proxy/WAF and enforce authentication and authorization at the backend.
- Audit Fabio route tables for catch-all or less restrictive fallback routes that reach protected backends; remove or protect them.
- Do not rely on allow= or auth= on proto=grpc routes until verified/fixed; enforce access control at the backend.
- Monitor access logs for crafted paths and unexpected 200 responses on protected resources.
Fixed versions
Sources
All live incidents on Threat Watch