在 Rancher Manager 中发现了一个缺陷: 的更新接口未强制保证用户资源中 (用户名)和 (主体标识符列表)字段的不变性。拥有 资源上 权限的用户,可以将任意外部身份提供方的主体(principal)注入到任意账户中。这样一来,当该主体的所有者下次登录时,其登录会话会被绑定到受害者的账户,并继承该账户的角色绑定(RBAC 权限)。 此问题影响 Rancher 2.15.1 之前的版本。
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-71404 | 8.7 HIGH | Rancher: Ownership-less ClusterRole overwrite via attacker-controlled cr-name annotation o |
| CVE-2026-75033 | 7.7 HIGH | Rancher: Cross-Cluster Secret Leakage via Namespace projectId Annotation Spoofing |
| CVE-2026-75035 | 7.7 HIGH | Rancher: ext.cattle.io/v1 Token store: cross-user token disclosure via label-selector scop |
| CVE-2026-75034 | 7.4 HIGH | Rancher: SAML Assertion Replay |
| CVE-2026-75036 | 5.3 MEDIUM | Fleet: DNS exfiltration via Sprig getHostByName in fleet.yaml Helm template preprocessing |
No comments yet