Black Hat USA 2026 | Breaking Multi-Tenancy Over and Over, and What We Can Learn From This
Implementing Kubernetes namespace-based multi-tenancy is challenging, and its isolation is generally considered less effective than control-plane isolation. That’s why the latter is often recommended … and also implemented? Not really, as workloads such as machine learning, pipelines, and scripting capabilities are increasingly common in enterprise environments. And they can introduce unobvious multi-tenancy in clusters.
So the question is: How can we securely isolate those workloads from each other? Pod Security Standards, Network Policies, and Admission Controls are well adopted, but are they sufficient?
The answer is no – this Briefing presents new vulnerabilities and real-world exploits in Kubeflow, Istio, and Traefik that violate trust boundaries between namespaces and workloads.
We will discuss these vulnerabilities in detail, together with the underlying conditions and root causes that render them exploitable.
Based on these examples, we will present a methodology for assessing complex environments with isolation problems and provide guidance on mitigating these issues.
Takeaway
We hope to provide the following to the audience:
– Thorough understanding of the security implications & pitfalls of namespace-based multi-tenancy
– How attackers can exploit typical configurations of some very popular projects/components
– How to properly harden these elements
– How to apply a consistent methodology to identify these types of issues in complex cluster deployments
Lorin Lehawany | Security Analyst, ERNW Enno Rey Netzwerke GmbH
Sven Nobis | Senior Security Analyst and Security Researcher, ERNW Enno Rey Netzwerke
https://blackhat.com/us-26/briefings/schedule/?#breaking-multi-tenancy-over-and-over-and-what-we-can-learn-from-this-54060Black HatRead More