<Vulnerability name="CVE-2026-85597">
    <DocumentDistribution xml:lang="en">Copyright © 2012 Red Hat, Inc. All rights reserved.</DocumentDistribution>
    <ThreatSeverity>Important</ThreatSeverity>
    <PublicDate>2026-09-04T11:30:00</PublicDate>
    <Bugzilla id="2528835" url="https://bugzilla.redhat.com/show_bug.cgi?id=2528835" xml:lang="en:us">
github.com/traefik/traefik: Traefik: Authentication bypass via TLS option conflict
    </Bugzilla>
    <CVSS3 status="draft">
        <CVSS3BaseScore>7.5</CVSS3BaseScore>
        <CVSS3ScoringVector>CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N</CVSS3ScoringVector>
    </CVSS3>
    <CWE>CWE-303</CWE>
    <Details xml:lang="en:us" source="Mitre">
Traefik before v2.11.55 and v3.0.0 through v3.7.10 contain a TLS option conflict resolution vulnerability that allows unauthenticated attackers to bypass client-certificate authentication by creating conflicting TLS options on multi-host routers. Attackers can reach protected backends by exploiting shared TLS resolution across multiple hostnames in a single router rule, causing the strict mTLS requirement to fall back to default options for all hosts.
    </Details>
    <Details xml:lang="en:us" source="Red Hat">
A flaw was found in Traefik. This vulnerability allows unauthenticated attackers to bypass client-certificate authentication. By creating conflicting Transport Layer Security (TLS) options on multi-host routers, attackers can exploit shared TLS resolution across multiple hostnames in a single router rule. This causes the strict mutual TLS (mTLS) requirement to fall back to default options, enabling access to protected backends.
    </Details>
    <Statement xml:lang="en:us">
A flaw was found in Traefik before v2.11.55 and v3.0.0 through v3.7.10, where multi-host router configurations fail to isolate TLS options. When shared router rules encompass multiple hostnames, conflicting TLS settings cause strict mTLS enforcement to regress to default configuration parameters across all associated endpoints. Within Red Hat environments utilizing affected Traefik versions, an unauthenticated remote attacker can exploit this fallback behavior to bypass client-certificate authentication controls and access protected backend services without valid credentials.
    </Statement>
    <Mitigation xml:lang="en:us">
Separate multi-host router rules into dedicated single-host routers so each domain explicitly defines its required TLS options without inheritance conflicts. Alternatively, enforce client-certificate authentication at an upstream ingress controller or API gateway before traffic reaches the Traefik router.
    </Mitigation>
    <PackageState cpe="cpe:/a:redhat:openshift_devspaces:3">
        <ProductName>Red Hat OpenShift Dev Spaces</ProductName>
        <FixState>Affected</FixState>
        <PackageName>devspaces/traefik-rhel9</PackageName>
    </PackageState>
    <PackageState cpe="cpe:/a:redhat:openshift_gitops:1">
        <ProductName>Red Hat OpenShift GitOps</ProductName>
        <FixState>Not affected</FixState>
        <PackageName>openshift-gitops-1/argo-rollouts-rhel8</PackageName>
    </PackageState>
    <PackageState cpe="cpe:/a:redhat:openshift_gitops:1">
        <ProductName>Red Hat OpenShift GitOps</ProductName>
        <FixState>Not affected</FixState>
        <PackageName>openshift-gitops-1/argo-rollouts-rhel9</PackageName>
    </PackageState>
    <References xml:lang="en:us">
https://www.cve.org/CVERecord?id=CVE-2026-85597
https://nvd.nist.gov/vuln/detail/CVE-2026-85597
https://github.com/traefik/traefik/security/advisories/GHSA-g55h-rg46-x9c5
https://www.vulncheck.com/advisories/traefik-before-2.11.55-mtls-bypass-via-tls-option-conflict
    </References>
</Vulnerability>