Telepresence: Traffic Manager gRPC has no auth — any pod claims arbitrary namespace and intercepts services, receiving victim environment…
Telepresence versions before 2.31.0 let any pod with cluster-network access to the Traffic Manager register in managed namespaces. Fixed in 2.31.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.31.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Attacker pod has cluster-network access to the Traffic Manager Traffic Manager manages all namespaces, as in the default cluster-wide deployment
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity8.5/10CVSS 8.5
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
CVE-2026-102340 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.5 (high) and affects telepresence; fixed in 2.31.0.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 2.31.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Telepresence's Traffic Manager, used for local development against Kubernetes or OpenShift clusters, can be attacked over the network by someone with low-level privileges. The attacker can register in any managed namespace, intercept services' traffic, and read a victim pod's container environment, including secrets, tokens, and API keys.
Read the original description
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.
What to do
Check whether your setup matches what the bug needs.
Attacker pod has cluster-network access to the Traffic Manager Traffic Manager manages all namespaces, as in the default cluster-wide deploymentUpgrade to a fixed version: 2.31.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- telepresenceio telepresence
fixed in 2.31.0
Evidence 6
- Advisory
- Repository
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-102340
Is CVE-2026-102340 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The Traffic Manager gRPC interface has no authentication, so a pod that can reach it can claim an arbitrary managed namespace and intercept services there. It can then receive their traffic and read the victim pod's environment, including secrets, tokens and API keys.Source: github.com
Which versions are affected by CVE-2026-102340?
telepresence: before 2.31.0.Source: cve.now feed data
Am I affected, and how do I check?
Telepresence versions before 2.31.0 are affected, most clearly in the default cluster-wide Traffic Manager deployment where all namespaces are managed. To check, run telepresence version to see the installed version and confirm whether the Traffic Manager manages all namespaces.Source: github.com
How do I fix CVE-2026-102340?
Upgrade Telepresence to 2.31.0 or later.Source: github.com
Why do the sources disagree?
The description says the gRPC interface is unauthenticated, but the CVSS vector records PR:L, which means low privileges are required. The sources conflict on whether a privilege is needed to exploit it.Source: github.com