CVE-2026-88979
Kubeflow Pipelines enables users to build and deploy portable, …
Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. From 2.17.0 until 2.18.0, the TensorBoard proxy token introduced by the incomplete remediation for CVE-2026-54745 uses MINIO_SECRET_KEY as its HMAC secret, whose bundled default is publicly known. In an authorization-disabled deployment using that default, an unauthenticated attacker can forge a token containing a chosen viewerName and namespace; the proxy constructs the destination from the viewerName plus the -service suffix, the namespace, and the configured cluster domain, then reads responses on port 80 under the /tensorboard/<viewer>/ path. Resource-name validation and path-traversal rejection remain enforced, authorization-enabled deployments still check access to the selected namespace, and unrestricted metadata access, writes, or service disruption are not established. This issue is fixed in version 2.18.0.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/kubeflow/pipelines/commit/c8effaed62476a8d8c99d3a6cfdd404a04ef99d8
- github.com/kubeflow/pipelines/pull/14346
- github.com/kubeflow/pipelines/releases/tag/2.18.0
- github.com/kubeflow/pipelines/security/advisories/GHSA-j429-j7xw-8j9h
- nvd.nist.gov/vuln/detail/CVE-2026-88979
- cve.org/CVERecord?id=CVE-2026-88979
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.