CVE-2026-102339: high-severity vulnerability in telepresenceio telepresence
Telepresence: Tunnel endpoint accepts caller-supplied session ID with no ownership proof — active client sessions hijackable
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.2epss 0.4%
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.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N
Affected products
telepresenceio · telepresenceRelated CVEs — telepresenceio telepresence
In the same product, most dangerous first.
References
https://github.com/telepresenceio/telepresence/commit/1312482488b771742dbedd3015f9a81a27532de6https://github.com/telepresenceio/telepresence/commit/36458b65a010d2b316af48cd90e193ba190785d9https://github.com/telepresenceio/telepresence/pull/4217https://github.com/telepresenceio/telepresence/releases/tag/v2.31.0https://github.com/telepresenceio/telepresence/security/advisories/GHSA-6j3h-rp73-6rvf