CVE-2026-102339 · Infrastructure
NO FIX YET · SEE WHAT TO DO
Telepresence, a tool for running local development against a remote Kubernetes or OpenShift cluster, fails to check that a caller owns a tunnel session before attaching to it. An attacker who obtains a valid active session ID can attach a routed tunnel and use that session's network routing into the cluster.
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 that run Telepresence against a Kubernetes or OpenShift cluster before version 2.31.0 are exposed, especially if the Traffic Manager's gRPC tunnel endpoint is reachable by others. Session IDs can leak through logs or cluster-internal channels, and the unauthenticated ArriveAsClient endpoint makes it easier to obtain or use one. Teams that do not use Telepresence, or run it only on fully isolated clusters, can skip it.
Not affected if telepresence-not-used, version-2.31.0-or-later
Who cares kubernetes, openshift, telepresence, traffic-manager
telepresence version and compare it against the fixed release.ArriveAsClient endpoint is reachable from outside the cluster network.2.31.0 or later.Telepresence enables local development against a remote Kubernetes or OpenShift cluster. Prior to 2.31.0, the Traffic Manager Tunnel gRPC streaming endpoint parses a session ID from the first bytes of a caller-controlled message in pkg/tunnel/message.go and passes it to state.Tunnel without verifying that the caller owns the active session. An attacker who obtains a valid active session ID through log leakage, cluster-internal channels, or the unauthenticated ArriveAsClient endpoint can attach a routed tunnel to that session and gain its network routing capabilities. UUID4 session IDs make cold brute force impractical. 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.