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.
Published: 2026-11-04
Score: 8.5 High
EPSS: n/a
KEV: No
Impact: Unauthorized access to secrets via service interception
Action: Immediate Patch
AI Analysis

Impact

Telepresence, a tool for local development against remote Kubernetes or OpenShift clusters, contains a flaw in its Traffic Manager gRPC API that listens on port 8081. The API accepts requests without verifying the caller’s identity. When an attacker registers with any pod that can reach the manager, the system stores a caller‑supplied namespace in the manager’s watchlist and allows creation of intercepts in any managed namespace without checking the Kubernetes RBAC session. This grants the attacker the ability to receive intercepted traffic and access the victim pod’s complete container environment, including secrets, tokens and API keys.

Affected Systems

All Telepresence releases before version 2.31.0 are vulnerable. The default cluster‑wide deployment manages every namespace, so any pod within the cluster network that can reach the manager can exploit the vulnerability.

Risk and Exploitability

The vulnerability has a CVSS score of 8.5, indicating a high severity. No EPSS score is available, and it is not listed in the CISA KEV catalog. The likely attack vector is an attacker operating any pod with network access to the Telepresence manager, enabling them to claim an arbitrary namespace, set up intercepts, receive traffic, and exfiltrate secrets. The lack of authentication and authorization makes exploitation straightforward for anyone who can reach the Traffic Manager service.

Generated by OpenCVE AI on November 4, 2026 at 21:20 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Telepresence to version 2.31.0 or newer to apply the fix for the unauthenticated gRPC API.
  • Restrict network access to the Traffic Manager by configuring firewall or Kubernetes network policies so that only authorized services can reach port 8081.
  • Implement strict RBAC policies that limit non‑admin service accounts from creating intercepts or managing namespaces, and review existing permissions to reduce privilege scope.

Generated by OpenCVE AI on November 4, 2026 at 21:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 04 Nov 2026 20:45:00 +0000

Type Values Removed Values Added
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.
Title Telepresence: Traffic Manager gRPC has no auth — any pod claims arbitrary namespace and intercepts services, receiving victim environment secrets
Weaknesses CWE-306
CWE-862
References
Metrics cvssV3_1

{'score': 8.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-11-04T20:39:55.525Z

Reserved: 2026-09-28T22:38:42.254Z

Link: CVE-2026-102340

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-04T21:17:40.683

Modified: 2026-11-04T21:17:40.683

Link: CVE-2026-102340

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-04T21:30:09Z

Weaknesses
  • CWE-306

    Missing Authentication for Critical Function

  • CWE-862

    Missing Authorization