rancher · Vulnerability
cve-program · CVE-2025-23389
PublishedA Improper Access Control vulnerability in SUSE rancher allows a local user to impersonate other identities through SAML Authentication on first login. This issue affects rancher: from 2.8.0 before 2.8.13, from 2.9.0 before 2.9.7, from 2.10.0 before 2.10.3.
Read the publisher's advisoryeuvd · EUVD-2025-6275
PublishedA Improper Access Control vulnerability in SUSE rancher allows a local user to impersonate other identities through SAML Authentication on first login. This issue affects rancher: from 2.8.0 before 2.8.13, from 2.9.0 before 2.9.7, from 2.10.0 before 2.10.3.
Read the publisher's advisorynvd · CVE-2025-23389
PublishedA Improper Access Control vulnerability in SUSE rancher allows a local user to impersonate other identities through SAML Authentication on first login. This issue affects rancher: from 2.8.0 before 2.8.13, from 2.9.0 before 2.9.7, from 2.10.0 before 2.10.3.
Read the publisher's advisoryosv · GHSA-mq23-vvg7-xfm4
Published### Impact A vulnerability in Rancher has been discovered, leading to a local user impersonation through SAML Authentication on first login. The issue occurs when a SAML authentication provider (AP) is configured (e.g. Keycloak). A newly created AP user can impersonate any user on Rancher by manipulating cookie values during their initial login to Rancher. This vulnerability could also be exploited if a Rancher user (present on the AP) is removed, either manually or automatically via the [User Retention feature](https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/enable-user-retention) with delete-inactive-user-after. More precisely, Rancher validates only a subset of input from the SAML assertion request; however, it trusts and uses values that are not properly validated. An attacker could then configure the saml_Rancher_UserID cookie and the saml_Rancher_Action cookie so that the user principal from the AP will be added to the user specified by the attacker (from saml_Rancher_UserID). Rancher can then be deceived by setting saml_Rancher_UserID to the admin's user ID and saml_Rancher_Action to testAndEnable, thereby executing the vulnerable code path and leading to privilege escalation. Note that the vulnerability impacts all SAML APs available in Rancher. However the following Rancher deployments are not affected: 1. Rancher deployments not using SAML-based AP. 2. Rancher deployments using SAML-based AP, where all SAML users are already signed in and linked to a Rancher account. Please consult the associated [MITRE ATT&CK - Technique - Access Token Manipulation: Token Impersonation/Theft](https://attack.mitre.org/techniques/T1134/001/) for further information about this category of attack. ### Patches This vulnerability is addressed by adding the UserID claim to a JWT signed token, which is protected against tampering. Patched versions include releases `v2.8.13`, `v2.9.7` and `v2.10.3`. ### Workarounds Rancher deployments that can't upgrade, could temporarily disable the SAML-based AP as a temporary workaround. However, upgrading is recommended. ### References If you have any questions or comments about this advisory: - Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries. - Open an issue in the [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository. - Verify with our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).
Read the publisher's advisoryosv · GO-2025-3490
PublishedRancher does not Properly Validate Account Bindings in SAML Authentication Enables User Impersonation on First Login in github.com/rancher/rancher. NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions. (If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.) The additional affected modules and versions are: github.com/rancher/rancher from v2.8.0 before v2.8.13, from v2.9.0 before v2.9.7, from v2.10.0 before v2.10.3.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2025-23389 · CVE overview and exploitation status
cve-program · CVE-2025-23389
- https://bugzilla.suse.com/show_bug.cgi?id=CVE-2025-23389
- https://github.com/rancher/rancher/security/advisories/GHSA-mq23-vvg7-xfm4
euvd · EUVD-2025-6275
- https://bugzilla.suse.com/show_bug.cgi?id=CVE-2025-23389
- https://github.com/rancher/rancher/security/advisories/GHSA-mq23-vvg7-xfm4
nvd · CVE-2025-23389
- https://bugzilla.suse.com/show_bug.cgi?id=CVE-2025-23389
- https://github.com/rancher/rancher/security/advisories/GHSA-mq23-vvg7-xfm4
osv · GHSA-mq23-vvg7-xfm4
- https://github.com/rancher/rancher/security/advisories/GHSA-mq23-vvg7-xfm4
- https://nvd.nist.gov/vuln/detail/CVE-2025-23389
- https://github.com/rancher/rancher/pull/48964
- https://github.com/rancher/rancher/pull/49030
- https://github.com/rancher/rancher/pull/49031
- https://github.com/rancher/rancher/commit/4b885322eaf9995a1054bb46e019841653dc0d10
- https://github.com/rancher/rancher/commit/cda77b743788feb8df8aedf9fd409ed0916a8723
- https://github.com/rancher/rancher/commit/f36b896a99441985a1658e1b8c504d77e52fee4f
- https://bugzilla.suse.com/show_bug.cgi?id=CVE-2025-23389
- https://github.com/rancher/rancher
- https://github.com/rancher/rancher/releases/tag/v2.10.3
- https://github.com/rancher/rancher/releases/tag/v2.8.13
- https://github.com/rancher/rancher/releases/tag/v2.9.7
- https://pkg.go.dev/vuln/GO-2025-3490
osv · GO-2025-3490
Related changes
Linked by CVE identifierNo related changes are available here.