CVE-2026-47237

HIGHPre-NVD 8.08.0
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 76% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
8.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Kubeflow Community Distribution helps users to install Kubeflow Platform in popular Kubernetes clusters. Prior to version 26.03-rc.1, a Kubeflow setup based on the official manifests or most other packaged Kubeflow distributions is vulnerable to authorization token stealing from any user of the Kubeflow UI or APIs, such as the Dashboard, Pipelines API, or Notebooks. With this token, the attacker can take over the user's account and the data that is processed by that user. The attacker needs a valid user with the `kubeflow-edit` role / Contributor role in a random Kubeflow namespace to perform this attack. This is given if _Automatic Profile Creation_ is enabled. Version 26.03-rc.1 fixes the issue.

CVSS v3
8.0
EG Score
8.0(medium)
EG Risk
52(Track*)
EG Risk 52/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity80% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
24.1%
KEV
Not listed

Published

July 21, 2026

Last Modified

July 23, 2026

Advisory Details (3)

Auto-updated Jul 21, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github.
github Patch Available🟡 PoC Available

Overly Permissive Istio Permissions Allows Kubeflow Authorization Token Stealing · Advisory · kubeflow/community-distribution · GitHub

https://github.com/kubeflow/community-distribution/security/advisories/GHSA-v824-8gxh-pgjw
github_pr Patch Available

Cleanup istio

Patch available: kubeflow/community-distribution v1.10.0-rc.3 (PR #3043 merged 2025-03-08)

https://github.com/kubeflow/community-distribution/pull/3043
github_commit Patch Available

commit 31b2411dda31 (kubeflow/community-distribution)

Patch available: kubeflow/community-distribution v1.10.0-rc.3 (contains commit 31b2411dda31)

https://github.com/kubeflow/community-distribution/commit/31b2411dda319bfeae8686ecdf3a39436ec32ce2

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:17 UTCEG score recompute
  3. 2026-07-22 22:57 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 21:22 UTCEG score recompute
  6. 2026-07-21 21:10 UTCEG score recompute
  7. 2026-07-21 21:08 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-47237?
CVE-2026-47237 is a high vulnerability published on July 21, 2026. Kubeflow Community Distribution helps users to install Kubeflow Platform in popular Kubernetes clusters. Prior to version 26.03-rc.1, a Kubeflow setup based on the official manifests or most other packaged Kubeflow distributions is vulnerable to authorization token stealing from any user of the…
When was CVE-2026-47237 disclosed?
CVE-2026-47237 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47237 actively exploited?
CVE-2026-47237 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-47237?
CVE-2026-47237 has a CVSS v3 base score of 8.0 (NVD).
How do I remediate CVE-2026-47237?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47237, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-47237

Explore →

Is Your Infrastructure Affected by CVE-2026-47237?

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