Summary
Traefik does not consistently enforce the crossProviderNamespaces allowlist for serversTransport references used by IngressRouteTCP services. A low-privileged Kubernetes user may therefore reference a forbidden file-provider transport and cause TCP traffic to use privileged settings such as backend mTLS credentials, SPIFFE identity, or PROXY-protocol behavior.
Affected context
The issue affects Traefik Kubernetes deployments that:
- Use
IngressRouteTCPresources - Permit namespace users to create or modify TCP routing resources
- Configure
serversTransportreferences across Traefik providers - Rely on
crossProviderNamespacesto restrict access to provider-owned resources
The authorization gap occurs when TCP route processing fails to apply the same cross-provider namespace restrictions enforced for HTTP routes.
Exploit preconditions
- Attack surface: Kubernetes custom resources processed by Traefik
- Required access: Low-privileged permission to create or modify an
IngressRouteTCPin a namespace outside the configured allowlist - Trigger point: Resolution of a TCP service's
serversTransportreference - Why exploitation is possible: The TCP reference path does not consistently enforce the configured cross-provider namespace authorization boundary, allowing a forbidden file-provider transport to be selected
Why this happens
The underlying bug is an authorization enforcement inconsistency between HTTP and TCP routing paths. The crossProviderNamespaces policy is applied to HTTP serversTransport references but omitted or insufficiently applied when resolving references from IngressRouteTCP services.
This maps to CWE-863: Incorrect Authorization, because a principal with limited namespace-level permissions can access a cross-provider resource that should be restricted by policy. The insecure pattern is enforcing an authorization rule in one resource-processing path while leaving an equivalent path unchecked.
Potential impact
- Unauthorized use of privileged backend transport settings
- Exposure or use of backend mTLS client certificates
- Impersonation of configured SPIFFE identities
- Unexpected PROXY-protocol behavior affecting backend trust decisions
- Circumvention of namespace-based administrative boundaries
- Potential access to protected services or sensitive backend data
General mitigation guidance
Mitigation generally focuses on consistent authorization enforcement across every resource type and provider-reference path.
Common defensive patterns include:
- Applying the same namespace and provider allowlist checks to HTTP, TCP, and other routing resources
- Rejecting unresolved or unauthorized cross-provider references by default
- Restricting which Kubernetes users and service accounts can create or modify
IngressRouteTCPresources - Separating privileged transport configurations from namespaces controlled by lower-trust users
- Avoiding unnecessary client certificates, SPIFFE identities, and proxy settings in shared or broadly accessible configurations
- Running Traefik and backend integrations with least privilege
- Treating provider references as security-sensitive inputs rather than ordinary configuration values
How teams detect issues like this
Organizations can look for this issue through:
- Static and configuration analysis that compares authorization checks across HTTP and TCP reference-resolution paths
- Code review signals where one route type validates
crossProviderNamespacesbut another uses a shared lookup without equivalent authorization - Kubernetes audit logs showing low-privileged users creating or modifying
IngressRouteTCPresources with cross-providerserversTransportreferences - Policy rules that restrict cross-provider references and privileged transport settings by namespace
- Runtime monitoring for unexpected use of file-provider transports, client certificates, SPIFFE identities, or PROXY-protocol options
Automated security review tools may help identify inconsistent authorization branches and unrestricted provider-resource lookups.

