CVE-2026-102340 · Infrastructure
NO FIX YET · SEE WHAT TO DO
Telepresence's Traffic Manager gRPC API on port 8081 accepts callers without authentication and does not check Kubernetes RBAC before creating intercepts. An attacker with network access to the manager in any managed namespace can receive intercepted traffic and read the victim pod's environment, including secrets, tokens and API keys.
first public Jul 22, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running Telepresence against a Kubernetes or OpenShift cluster, especially with the default cluster-wide Traffic Manager that manages all namespaces. Any workload pod with cluster network access to the manager can exploit it without credentials, so the exposure is wider than the developers using Telepresence. Clusters that do not run Telepresence, or run it on a version at or above 2.31.0, are not affected.
Not affected if no-telepresence-deployed, version-2.31.0-or-later
Who cares kubernetes, openshift, self-hosted, telepresence
telepresence version and compare it to the fixed release.kubectl get deploy traffic-manager -A.2.31.0 or later.Telepresence enables local development against a remote Kubernetes or OpenShift cluster. Prior to 2.31.0, the Traffic Manager gRPC API on port 8081 accepts unauthenticated cluster-network callers, ArriveAsClient stores a caller-supplied Namespace using only the ManagesNamespace manager watchlist check, and CreateIntercept can target any managed namespace without checking the session's Kubernetes RBAC. An attacker operating any pod with network access to the manager can register in an arbitrary managed namespace, create service intercepts, receive intercepted traffic, and obtain the victim pod's complete container environment, including secrets, tokens, and API keys. The default cluster-wide deployment manages all namespaces. This vulnerability is fixed in 2.31.0.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.