CVE-2026-112778
Description
A flaw was found in Traefik. An authenticated attacker with permissions to create or update Kubernetes Ingress or Service resources can bypass multi-tenant isolation boundaries due to missing namespace validation in resource annotations. By referencing configuration objects in other namespaces, the attacker can access sensitive credentials and reuse client certificates belonging to other tenants.
Statement
This vulnerability is rated as an Important severity because an authenticated tenant can breach isolation boundaries to access secrets or TLS certificates belonging to other namespaces. In environments where Traefik serves as the ingress controller, users permitted to define ingress specifications can supply unvalidated annotations that reference external middleware or transport configurations. Standard Red Hat OpenShift environments utilize the native OpenShift Ingress Operator rather than Traefik and are not exposed in default configurations.
Understanding the Weakness (CWE)
Access Control
Technical Impact: Bypass Protection Mechanism
Access control checks for specific user data or functionality can be bypassed.
Access Control
Technical Impact: Gain Privileges or Assume Identity
Horizontal escalation of privilege is possible (one user can view/modify information of another user).
Access Control
Technical Impact: Gain Privileges or Assume Identity
Vertical escalation of privilege is possible if the user-controlled key is actually a flag that indicates administrator status, allowing the attacker to gain administrative access.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
