Summary
A TLS option conflict resolution flaw in Traefik can cause strict client-certificate authentication to be replaced by default TLS options on multi-host routers. An unauthenticated network attacker may then reach backends that were intended to require mutual TLS when conflicting options are associated with different hostnames.
Affected context
The issue occurs in Traefik deployments that use multi-host router rules with TLS options defined for multiple hostnames. It becomes risky when those hostnames resolve conflicting TLS settings and the router's option-selection behavior falls back to a default configuration rather than preserving the strict client-certificate requirement. The affected version ranges are Traefik releases before v2.11.55 and releases from v3.0.0 through v3.7.10.
Exploit preconditions
- Attack surface: Network-accessible Traefik entrypoints and routed backend services
- Required access: No authentication is required when the relevant router is reachable
- Trigger point: A request targeting a multi-host router with conflicting TLS options
- Required configuration: At least one protected backend relies on client-certificate authentication, while TLS options are shared or resolved across multiple hostnames
- Why exploitation is possible: Conflict resolution can select default TLS behavior for the router, preventing the intended strict mutual-TLS policy from being enforced
Why this happens
The underlying bug is an authorization-policy enforcement failure in TLS option resolution. When a single router represents multiple hostnames with conflicting TLS requirements, the implementation can resolve the conflict by falling back to default options rather than maintaining the strongest configured authentication policy. This maps to CWE-863: Incorrect Authorization, because access control requirements are not consistently enforced for requests reaching protected resources.
Potential impact
- Unauthenticated clients may reach backends intended to require client certificates
- Protected administrative or internal services could be exposed through affected routes
- Backend data or operations may be accessed without the intended identity verification
- Trust boundaries between public and mutually authenticated services could be weakened
General mitigation guidance
Mitigation generally focuses on ensuring that TLS authentication policies are explicit, deterministic, and fail closed when configuration conflicts occur.
Common defensive patterns include:
- Using separate routers when hostnames require different TLS authentication policies
- Avoiding ambiguous sharing of TLS options across hosts with different trust requirements
- Treating conflicting security settings as configuration errors rather than selecting permissive defaults
- Requiring client certificates at the appropriate entrypoint or backend boundary
- Applying least-privilege routing so publicly reachable routers cannot expose sensitive services
- Testing effective TLS policy for every hostname, including negative tests that omit client certificates
How teams detect issues like this
Organizations can identify this class of issue through:
- Configuration analysis that flags multi-host routers with conflicting TLS options
- Static and policy checks for protected backends routed through default or non-mTLS TLS settings
- Code review signals involving fallback behavior after TLS option conflicts
- Integration tests that verify each hostname enforces its intended client-certificate policy
- Network monitoring for successful connections to mTLS-protected routes without client-certificate authentication
- Automated configuration review tools that compare declared TLS policies with effective runtime behavior

