On this page (7 sections)

Fabio, the HTTP(S) and TCP router used to front applications registered in Consul, has a critical access-control flaw. According to the GitHub advisory, versions before 1.7.3 choose a route using the raw, unnormalized request path. A request written with dot segments, an encoded dot or a doubled slash can land on a different, less restrictive route and skip the per-route IP ACL and basic-auth checks.

If you run Fabio in front of admin panels, internal dashboards or any path protected with allow, deny or auth options, this affects you. The fix is available in 1.7.3, and the advisory also links a 1.8.0 release.

What happened

The advisory was published on GitHub on Aug 9, 2026 and later reached the National Vulnerability Database (Nov 19, 2026) and the GitHub Advisory Database (Nov 20, 2026). The reporter states the bypass needs no authentication and completely defeats the access control the operator configured. The CVSS v3 metrics listed are network attack vector, low complexity, no privileges, no user interaction, high confidentiality and integrity impact, and no availability impact.

Coverage so far comes from the advisory itself, so treat details beyond it as unconfirmed. The advisory notes that AI assistance was used in the audit and drafting, and that the reporter manually verified the finding against the source and reproduced it against a running Fabio binary.

How the weakness works

This is a path normalization mismatch, a well-known class of bug. Two components read the same URL differently: the router and the backend. Fabio decides which route a request belongs to by looking at the literal path string. The backend, however, cleans up that path (resolving . and .. segments, decoding encoded dots, collapsing repeated slashes) before deciding what file or page to serve.

In Fabio the access checks are attached to the route that was selected, not to the resource that is finally served. According to the advisory, the lookup in route/table.go uses req.URL.Path, and the ACL and basic-auth checks in proxy/http_proxy.go are applied to whichever target that lookup returned. The raw path is then forwarded to the origin unchanged. So a request that does not literally match the protected prefix falls through to a broader route with no ACL and no auth, and the backend later normalizes it into the protected resource.

The advisory lists the weakness classes as CWE-41, CWE-289 and CWE-863. It also points to similar past issues in other proxies, Traefik CVE-2023-47106 and Envoy CVE-2019-9901, which shows this is a recurring pattern for reverse proxies rather than something unique to Fabio.

Who is realistically exposed

There is an important precondition. The advisory says a less restrictive route must reach the same backend so the crafted path has somewhere to fall through to. Where no such fallback exists, the request returns a 404 instead. The reporter points out that this is the two-tag urlprefix- layout that Fabio's own access-control documentation tells operators to configure, so a typical setup following the docs can meet the condition.

You are most likely exposed if all of these are true:

  • You run a Fabio version earlier than 1.7.3.
  • You protect a path prefix (for example an admin area) with per-route allow/deny IP rules or auth= basic authentication.
  • A broader route, such as a catch-all /, points at the same backend without those restrictions.
  • The backend normalizes paths before serving, which most web servers and frameworks do.

The reporter also made two secondary observations in the advisory: X-Forwarded-Prefix is passed through from the client on non-strip routes, and the gRPC proxy path never calls either authorization gate, so allow= and auth= on a proto=grpc route are silently unenforced. These are described as observations, not as part of this CVE's fix, so check the release notes for your version rather than assuming they are resolved.

How to check your exposure

Start by finding out which version you run and whether your routing table has the risky shape. If Fabio is built into your own Go project, this read-only command lists the module version in use. Run it in the project directory and look for a version below 1.7.3.

Show the Fabio module version in a Go project (run in the project directory)Shell
go list -m github.com/fabiolb/fabio

If you run a prebuilt binary or container image, check the image tag or release you deployed against your deployment records, and compare it with the v1.7.3 release.

Next, review your route definitions. Look for any protected prefix (with allow, deny or auth options) that shares a backend with a broader route that has no such options. Those are the pairs that can be bypassed.

Finally, search access logs for signs of attempts. This read-only grep looks for requests containing dot segments, encoded dots or doubled slashes in the path. Adjust the log path to your setup; any match on a protected area is worth investigating, though some matches will be harmless scanner noise.

Search a request log for suspicious path forms (adjust the log file path)Shell
grep -E '(/\./|/\.\./|%2e|%2E|//)' /var/log/fabio/access.log
Logs may record the path after other components have already normalized it, so an empty result does not prove nobody tried this. Also, a 200 response to such a request is the signal to look at, since a blocked request would normally show 401, 403 or 404.

What to do now

  1. Upgrade Fabio to 1.7.3 or later (the advisory also references a 1.8.0 release) and redeploy every instance.
  2. Review each route that uses allow, deny or auth= and note which broader routes share its backend.
  3. Where you cannot upgrade immediately, remove or narrow fallback routes that reach the same backend as a protected one, so crafted paths return 404 rather than falling through.
  4. Add a second layer of access control at the backend or another gateway, so the protected resource does not rely only on Fabio's per-route checks.
  5. Do not rely on allow= or auth= for proto=grpc routes until you have confirmed they are enforced in your version.
  6. Search access logs for requests to protected areas that succeeded without credentials, and rotate any secrets exposed by those pages if you find evidence of access.
  7. Restrict who can reach Fabio's listeners at the network level, so internal-only services are not reachable from the internet.
Caution. Redeploying or restarting a router in front of production traffic can cause brief interruptions. Roll out the upgrade instance by instance and confirm routes still resolve as expected, since changing route tables can also change which traffic reaches which backend.

The advisory's suggested remediation for developers is to normalize the path before route lookup, decoding percent-encoded dot segments and applying path.Clean, so that route and access decisions are made on the same form of the path the backend will use. The same principle applies to your own gateways: make the access decision on the canonical path, never on the raw string.

Detection and monitoring afterwards

After patching, verify behavior from the outside. With your own authorization, request a protected path without credentials and confirm you get 401 or 403, then confirm that unusual path forms for the same resource are also refused or return 404. Repeat this check after every routing change, since a new fallback route can quietly reintroduce the problem.

Keep logging enabled on Fabio and your backends, and alert on successful responses to protected prefixes that have no matching authenticated session. A read-only scan of a site you control can help you spot exposed admin paths from the outside, and monitoring for header and certificate changes helps you notice unexpected changes to what your edge serves. These do not replace patching. For wider background, see our guide on what a WAF can and cannot do.

Timeline

Key dates from the GitHub advisory
DateEvent
Aug 9, 2026Advisory published in the fabiolb/fabio repository
Nov 19, 2026Published by the National Vulnerability Database
Nov 20, 2026Published to and reviewed in the GitHub Advisory Database

The advisory also notes an earlier, separate Fabio issue, CVE-2026-62987 (GHSA-fq95-v8xc-jm3v), fixed in v1.7.2. It concerns stripping of certain client-IP, TLS and request-ID headers and is described as an independent defect, so patching it does not cover this one. Fix details are in the fix commit and the project's security advisory.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-104099 - GitHub Advisory Databasegithub.com
  • Fabio
  • CVE-2026-104099
  • access control
  • path normalization
  • Go
  • Consul