CVE-2026-102340

HIGHPre-NVD 8.58.5
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.5 from GitHub Security Advisory (severity: HIGH) published 2026-11-09. A secondary CVSS source baseline 8.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-117096 (ENISA EUVD) · GHSA-j8j4-rw65-56r6 (GitHub Security Advisories)Source: ENISA EUVD

8.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.5
EG Score
8.5HIGHhigh confidence
EG Risk
38
EG Risk 38/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity85% × 45%
Impact severity (EG Severity): CVSS 8.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.5): severity, escalated by confirmed exploitation. This CVE's 8.5 is its impact severity (EG Severity), not escalated.

EG Severity
8.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 4, 2026

Last Modified

November 12, 2026

Advisory Details (6)

Auto-updated Nov 4, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub release Patch Available

v2.31.0

Patch available: telepresenceio/telepresence v2.31.0

https://github.com/telepresenceio/telepresence/releases/tag/v2.31.0
GitHub commit

commit 6871235b674a (telepresenceio/telepresence)

Fix landed in telepresenceio/telepresence commit 6871235b674a — awaiting tagged release

https://github.com/telepresenceio/telepresence/commit/6871235b674a6e843908d09696354c4b0f91578c
GitHub commit

commit 36458b65a010 (telepresenceio/telepresence)

Fix landed in telepresenceio/telepresence commit 36458b65a010 — awaiting tagged release

https://github.com/telepresenceio/telepresence/commit/36458b65a010d2b316af48cd90e193ba190785d9
GitHub commit

commit 04ec3464fe88 (telepresenceio/telepresence)

Fix landed in telepresenceio/telepresence commit 04ec3464fe88 — awaiting tagged release

https://github.com/telepresenceio/telepresence/commit/04ec3464fe8878fdc96420cdc8036edefa0dc9ae
GitHub pull request

Release v2.31.0

Fix merged in telepresenceio/telepresence PR #4217 on 2026-07-22 — awaiting tagged release

https://github.com/telepresenceio/telepresence/pull/4217
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Traffic Manager gRPC has no auth — any pod claims arbitrary namespace and intercepts services, receiving victim environment secrets · Advisory · telepresenceio/telepresence · GitHub

https://github.com/telepresenceio/telepresence/security/advisories/GHSA-j8j4-rw65-56r6

Vendor Advisories for CVE-2026-102340(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/telepresenceio/telepresence @ 2.31.0 (fixes < 2.31.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/telepresenceio/telepresence—
  • every version up to 2.31.0: fixed in 2.31.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 13× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-11-12 20:08 UTCEchelonGraph re-scored
  3. 2026-11-12 20:08 UTCGHSA enrichmentGHSA-j8j4-rw65-56r6 · GitHub severity HIGH · GitHub CVSS 8.5
  4. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  5. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  6. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  7. 2026-11-09 22:45 UTCEchelonGraph re-scored
  8. 2026-11-09 22:45 UTCGHSA enrichmentGHSA-j8j4-rw65-56r6 · GitHub severity HIGH · GitHub CVSS 8.5
  9. 2026-11-09 17:27 UTCEchelonGraph re-scored
  10. 2026-11-09 17:05 UTCEchelonGraph re-scored
  11. 2026-11-09 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  12. 2026-11-08 16:37 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  13. 2026-11-07 16:37 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  14. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  15. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  16. 2026-11-04 22:03 UTCENISA EUVD ID recordedEUVD-2026-117096 · Source: ENISA EUVD
  17. 2026-11-04 21:26 UTCEchelonGraph re-scored
  18. 2026-11-04 20:46 UTCEchelonGraph re-scoredFirst assessed: 8.5 HIGH
  19. 2026-11-04 20:45 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-102340?
CVE-2026-102340 is a high-severity vulnerability; its CVE record was published on November 4, 2026. 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…
When was the CVE record for CVE-2026-102340 published?
The CVE record for CVE-2026-102340 was published on November 4, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 12, 2026; the record at its source may have been updated since.
Is CVE-2026-102340 actively exploited?
CVE-2026-102340 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102340?
CVE-2026-102340 has a CVSS base score of 8.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-102340?
A fix for CVE-2026-102340 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-102340 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-102340

Explore →

Is Your Infrastructure Affected by CVE-2026-102340?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs