CriticalCVE-2026-104099

    fabio: Authentication Bypass by Alternate Name (CVE-2026-104099)

    Published Last modified Sources: CVE.org, EUVD, OSV, Hersteller

    Share

    What is affected, what to do

    Update fabio to version 1.7.3, github.com/fabiolb/fabio to version 1.7.3.

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    9.1

    XIEM Effective CVSS

    Highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    9.1

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: CVE.org, EUVD, OSV, Hersteller

    —

    EPSS score

    No value is available for this vulnerability.

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    75.50 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    9.1 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    9.1
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 19 November 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-289, CWE-41, CWE-863

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    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:

    // proxy/http_proxy.go
    if t.AccessDeniedHTTP(r) {                      // line 111, per-route allow / deny:ip ACL
        http.Error(w, "access denied", http.StatusForbidden)
        return
    }
    if !t.Authorized(r, w, p.AuthSchemes) {          // line 116, per-route auth= basic auth
        http.Error(w, "authorization failed", http.StatusUnauthorized)
        return
    }
    

    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.

    Verification

    Verified end to end against the real binary at HEAD, not a synthetic unit test. fabio was built and run with static routes against a python3 -m http.server origin, driven with curl --path-as-is: on a basic-auth route, /admin/ returned 401 without credentials and 200 with valid credentials (controls correct), while all four crafted paths returned 200 with the protected page and NO credentials; on an ACL route, /admin/ returned 403 and all four crafted variants returned 200.

    Precondition, stated honestly: a less restrictive route must reach the same backend so the crafted path has somewhere to fall through to. That is exactly the two-tag urlprefix- shape fabio's own access-control documentation instructs operators to configure. Where no fallback route exists the request 404s instead.

    Suggested fix

    Normalize the path before route lookup: decode percent-encoded dot segments and apply path.Clean, then match. Whether the normalized or original path is forwarded upstream is a separate decision, but the LOOKUP must run on the normalized form, because the ACL and auth decisions are derived from it. Also lowercase and strip the port and any trailing dot from the request host before host matching. Secondary observations: X-Forwarded-Prefix is passed through from the client on non-strip routes; the gRPC proxy path never calls either authorization gate, so allow=/auth= on a proto=grpc route are silently unenforced.

    Dedup note

    The obvious residual of CVE-2025-48865 is already taken: CVE-2026-62987 / GHSA-fq95-v8xc-jm3v (published 2026-07-03) covers the Connection-header strip of proxy.header.clientip/tls/requestid, fixed in v1.7.2. Do not re-report that. The finding above is a different and independent defect.

    Tooling

    AI assistance was used while investigating. The bypass was reproduced against the real fabio binary with a live backend, including the 401-vs-200 and 403-vs-200 controls, and the reporter separately confirmed at HEAD that lookup takes req.URL.Path, that both gates derive from the returned target, that the raw path is forwarded, and that path.Clean appears nowhere in the repository.

    The reporter manually verified this finding against the project's source at the location cited above before reporting it; the AI assistance noted above was for the audit and the drafting.

    Source: cvelistv5, ENISA EUVD, NVD (NIST), CVE.org (MITRE), OSV (Open Source Vulnerabilities), GitHub Security Advisories

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    fabiolbfabio
    • < 1.7.3
    • 1.7.3
    gogithub.com/fabiolb/fabio
    • < 1.7.3
    • —
    • 1.7.3
    • 1.7.3

    Vendors and products

    Weakness classes (CWE)

    • CWE-289Authentication Bypass by Alternate Name

      Base

      The product performs authentication based on the name of a resource being accessed, or the name of the actor performing the access, but it does not properly check all possible names for that resource or actor.

      Entry at MITRE CWE-289
    • CWE-41Improper Resolution of Path Equivalence

      Base

      The product is vulnerable to file system contents disclosure through path equivalence. Path equivalence involves the use of special characters in file and directory names. The associated manipulations are intended to generate multiple names for the same object.

      Entry at MITRE CWE-41
    • CWE-863Incorrect Authorization

      Class

      The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

      Entry at MITRE CWE-863

    References & sources

    • github.comfabiolb/fabio/commit/f00ce1a446a4b7a3bccbefbb7bfe4a5e0e3fd817x_refsource_MISC, euvd, web
    • github.comfabiolb/fabio/releases/tag/v1.7.3x_refsource_MISC, euvd, web
    • github.comfabiolb/fabio/releases/tag/v1.8.0x_refsource_MISC, euvd, web
    • github.comfabiolb/fabio/security/advisories/GHSA-4hrh-34w3-5ww8x_refsource_CONFIRM, euvd, web
    • NVD (NIST)vuln/detail/CVE-2026-104099advisory
    • github.comfabiolb/fabiopackage

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: none known, automatable: yes

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentadded
      —
      {"id":"CVE-2026-104099","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-11-19T20:31:04.929666Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. ReceivedGitHub

      Show 10 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      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.
      CVSSadded
      —
      AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
      Weakness type (CWE)added
      —
      CWE-289
      Weakness type (CWE)added
      —
      CWE-41
      Weakness type (CWE)added
      —
      CWE-863
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/104xxx/CVE-2026-104099.json">CVE-2026-104099</a>
      Referenceadded
      —
      https://github.com/fabiolb/fabio/commit/f00ce1a446a4b7a3bccbefbb7bfe4a5e0e3fd817
      Referenceadded
      —
      https://github.com/fabiolb/fabio/releases/tag/v1.7.3
      Referenceadded
      —
      https://github.com/fabiolb/fabio/releases/tag/v1.8.0
      Referenceadded
      —
      https://github.com/fabiolb/fabio/security/advisories/GHSA-4hrh-34w3-5ww8

      Source identifier: security-advisories@github.com

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-104099
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-104099"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-104099.svg?lang=en" alt="CVE-2026-104099 – NEOSEC Intel" height="20"></a>