SUSE Rancher Fleet 集群引用了一个 kubeconfig 密钥(secret),控制器使用该密钥在目标集群中安装并管理 Fleet 代理。然而,该控制器未对 Fleet Cluster 对象可引用的 kubeconfig 密钥进行充分限制。因此,由普通用户控制的命名空间中定义的 Fleet 集群,可能被关联到管理集群自身的管理员凭据。这将导致控制器代表该用户管理管理集群,并在该集群中以提升的权限运行该用户的 Fleet 内容。此问题影响 SUSE Rancher Fleet 0.16.0 至 0.
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.
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-88811 | 9.1 CRITICAL | Rancher credentials disclosed to third-party hosts by the Rancher Manager meta proxy |
| CVE-2026-88809 | 7.6 HIGH | Rancher meta proxy allowlist bypass leading to server-side request forgery |
| CVE-2026-88810 | 7.2 HIGH | Privilege escalation in downstream clusters via GlobalRole inheritedNamespacedRules |