CVE-2026-47237
Auth token theft via Kubeflow UI/API enabling account takeover
Is CVE-2026-47237 being exploited?
Not confirmed. CVE-2026-47237 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.40% probability of exploitation in the next 30 days.
How severe is CVE-2026-47237?
CVE-2026-47237 is rated High with a CVSS score of 8.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-47237?
Yes. A fix has been recorded for CVE-2026-47237. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-47237 affect?
CVE-2026-47237 affects Kubeflow Community Distribution < 26.03-rc.1, Kubeflow Dashboard, Kubeflow Pipelines API, Kubeflow Notebooks, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-47237?
Upgrade to 26.03-rc.1+; disable Automatic Profile Creation; audit kubeflow-edit privileges.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers with kubeflow-edit role can steal user auth tokens via UI/APIs to hijack accounts and access pipelines, notebooks, and data.
Immediate action required
- affected< 26.03-rc.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.