Security Digest · Vulnerability record

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

Fabio is an HTTP(S) and TCP router for deploying applications managed by consul.

CVSS 9.1 Critical EPSS 0.6% · p48

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
  • EPSS 0.6%, percentile 48: FIRST’s model estimates a 0.6% chance of exploitation activity in the next 30 days, higher than 48% of all scored CVEs (low). EPSS is a probability, not a verdict.
  • Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
  • Only applies if your dependency tree includes github.com/fabiolb/fabio (Go) < 1.7.3, fixed in 1.7.3. Check your lockfile, including transitive dependencies.

What it is

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/httpproxy.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.

From the GitHub advisory

Summary

Route selection uses the raw un-normalized request path, and the per-route ACL and basic-auth gates hang off that selection, so a dot-segment, encoded-dot, or double-slash variant of a protected path selects a different route, skips both gates, and is forwarded to the backend which normalizes and serves the protected resource. Unauthenticated; complete bypass of the access control the operator configured. Confirmed at HEAD b841544. Direct peers: Traefik CVE-2023-47106, Envoy CVE-2019-9901.

The defect

fabio never normalizes the request path. A repository-wide search for path.Clean returns zero results. Route selection uses the raw path (route/table.go line 487: if target = t.lookup(h, req.URL.Path, pick, match); target != nil {). Both access-control gates are properties of the target that lookup returned:

and the same raw path is forwarded verbatim (Path: r.URL.Path at line 142). So /./admin/, /%2e/admin/, //admin/ and /x/../admin/ do not match the protected /admin route. They fall through to the catch-all / route, which carries no ACL and no auth, and fabio forwards the un-normalized path to the origin, which normalizes it and serves the protected resource.

Weakness type: CWE-41, CWE-289, CWE-863.

Product: github.com/fabiolb/fabio (Go) · Assigned by: GitHub_M · Published: 2026-11-19

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
Gogithub.com/fabiolb/fabio< 1.7.31.7.3
VendorProductAffected versions (per CVE record)
fabiolbfabio< 1.7.3

Severity scores

Scored byCVSSScoreVector
GitHub_M3.19.1 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
GitHub3.19.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Privileges required: none (no login)
  • User interaction: none
  • Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
  • FIRST EPSS (model of 2026-11-21): 0.57% probability of exploitation activity in the next 30 days; percentile 48.

Timeline

  • — CVE record last updated
  • — CVE record published by GitHub_M
  • — GitHub-reviewed advisory GHSA-4hrh-34w3-5ww8 published (critical)

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

  1. GitHub Advisory GHSA-4hrh-34w3-5ww8 github.com
  2. CVE.org record CVE-2026-104099 cve.org
  3. NVD entry CVE-2026-104099 nvd.nist.gov

Other references from the CVE record and advisory

  1. github.com github.com
  2. github.com github.com
  3. github.com github.com
  4. github.com github.com

Critical Go advisories · Today’s Security Digest