CVE-2026-47237

Received Received - Intake

Authorization Token Theft in Kubeflow Community Distribution

Publication date: 2026-07-21

Last updated on: 2026-07-21

Assigner: GitHub, Inc.

Description

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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-21

Last Modified

2026-07-21

Generated

2026-07-22

AI Q&A

2026-07-22

EPSS Evaluated

N/A

NVD

CVE-2026-47237

Affected Vendors & Products

Vendor	Product	Version / Range
kubeflow	kubeflow	to 26.03-rc.1 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-266	A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor.

Attack-Flow Graph

Executive Summary

Kubeflow Community Distribution versions before 26.03-rc.1 have a flaw where authorization tokens can be stolen from any user interacting with the Kubeflow UI or APIs, such as Dashboard, Pipelines API, or Notebooks. This allows attackers to take over user accounts and access data processed by those users. The attack requires a valid user with the kubeflow-edit role or Contributor role in a Kubeflow namespace, which is automatically created if Automatic Profile Creation is enabled.

Impact Analysis

If you use Kubeflow versions before 26.03-rc.1, an attacker could steal your authorization token and gain full control over your Kubeflow account. This could lead to unauthorized access to your data, manipulation of pipelines, notebooks, or other resources, and potential data breaches or loss of sensitive information.

Compliance Impact

This vulnerability could lead to unauthorized access to personal or sensitive data, violating GDPR and HIPAA requirements for data protection and access control. Organizations using affected Kubeflow versions may face compliance violations, legal penalties, and reputational damage due to potential data breaches.

Mitigation Strategies

Upgrade to Kubeflow version 26.03-rc.1 or later to fix the authorization token stealing vulnerability. Disable Automatic Profile Creation if enabled to reduce attack surface.

Hi! I’m here to help you understand CVE-2026-47237. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70