Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-88979— Kubeflow Pipelines: Unauthenticated SSRF vulnerability in Kubeflow Pipelines TensorBoard proxy

Quick assessment

Affected
kubeflow pipelines
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Kubeflow Pipelines 允许用户构建和部署可移植、可扩展的机器学习工作流。在 2.17.0 至 2.18.0 版本期间，由于对 CVE-2026-54745 的修复不完整，TensorBoard 代理令牌使用了 MINIO_SECRET_KEY 作为其 HMAC 密钥，而该密钥的捆绑默认值已公开。在禁用授权且使用该默认值的部署环境中，未认证的攻击者可伪造包含指定 viewerName 和命名空间的令牌；代理会根据 viewerName 加上 "-service" 后缀、命名空间以及配置的集群域名构造目

CVSS 5.8 · Medium
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-88979

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Kubeflow Pipelines: Unauthenticated SSRF vulnerability in Kubeflow Pipelines TensorBoard proxy
Source: CVE Program / CVE List V5
Vulnerability Description
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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
使用硬编码的凭证
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
kubeflow pipelines >= 2.17.0, < 2.18.0 -

II. Public POCs for CVE-2026-88979

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-88979

请登录查看更多情报信息。

Vendor Pages for CVE-2026-88979 (1)

Other References for CVE-2026-88979 (3)

Same Patch Batch · kubeflow · 2026-11-05 · 9 CVEs total

CVE-2026-77596 9.6 CRITICAL Kubeflow Pipelines API server lacks authorization for shared pipeline uploads
CVE-2026-88981 8.6 HIGH Kubeflow Pipelines: Unauthenticated SSRF through artifact provider endpoints
CVE-2026-88980 8.6 HIGH Kubeflow Pipelines: Unauthenticated server-side request forgery in the frontend http/https
CVE-2026-88984 7.2 HIGH Kubeflow Pipelines: RBAC bypass on shared pipelines allows any authenticated user to delet
CVE-2026-88985 6.5 MEDIUM Kubeflow Pipelines: SQL injection through unvalidated pagination tokens in Kubeflow Pipeli
CVE-2026-88986 6.1 MEDIUM Kubeflow Pipelines: Reflected XSS in the frontend pod information and events error respons
CVE-2026-88982 5.4 MEDIUM Kubeflow Pipelines: Cross-tenant execution-cache poisoning / output substitution via a nam
CVE-2026-88983 5.0 MEDIUM Kubeflow Pipelines — API server fetches a caller-supplied pipelineURL without host validat

IV. Related Vulnerabilities

Same product: pipelines
Same vendor: kubeflow
Same weakness: CWE-798