Rancher's SAML-based login via CLI can be denied by unauthenticated users
cve-program · CVE-2025-23387
PublishedA Exposure of Sensitive Information to an Unauthorized Actor vulnerability in SUSE rancher allowed unauthenticated users to list all CLI authentication tokens and delete them before the CLI is able to get the token value.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-10799
PublishedA Exposure of Sensitive Information to an Unauthorized Actor vulnerability in SUSE rancher allowed unauthenticated users to list all CLI authentication tokens and delete them before the CLI is able to get the token value.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-23387
PublishedA Exposure of Sensitive Information to an Unauthorized Actor vulnerability in SUSE rancher allowed unauthenticated users to list all CLI authentication tokens and delete them before the CLI is able to get the token value.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-5qmp-9x47-92q8
Published### Impact A vulnerability has been identified within Rancher where it is possible for an unauthenticated user to list all CLI authentication tokens and delete them before the CLI is able to get the token value. This effectively prevents users from logging in via the CLI when using rancher token as the execution command (instead of the token directly being in the kubeconfig). Note that this token is not the kubeconfig token and if an attacker is able to intercept it they can't use it to impersonate a real user since it is encrypted. This happens because for SAML-based authentication providers, the login flow from the CLI works by generating a link to be pasted in the browser, and then polling every 10 seconds for the `/v3-public/authTokens/<token name>` endpoint. The `<token name>` is randomly generated by the CLI. Once the login flow succeeds, Rancher creates an auth token (with an encrypted token value). The CLI then deletes the authToken. Rancher deployments using only the local authentication provider, or non-SAML-based authentication providers, are not impacted by this vulnerability. SAML-based users not using the CLI are also not impacted. Please consult the associated [MITRE ATT&CK - Technique - Account Access Removal](https://attack.mitre.org/techniques/T1531/) for further information about this category of attack. ### Patches The fix involves removing GET and DELETE methods for the authTokens collection. Patched versions include releases `v2.8.13`, `v2.9.7` and `v2.10.3`. ### Workarounds Users can refrain from using the Rancher CLI to log in as a workaround. Otherwise, users are advised to upgrade to a patched version of Rancher Manager. ### 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-3489
PublishedRancher's SAML-based login via CLI can be denied by unauthenticated users 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-23387 · CVE overview and exploitation status
cve-program · CVE-2025-23387
- https://bugzilla.suse.com/show_bug.cgi?id=CVE-2025-23387
- https://github.com/rancher/rancher/security/advisories/GHSA-5qmp-9x47-92q8
euvd · EUVD-2025-10799
- https://bugzilla.suse.com/show_bug.cgi?id=CVE-2025-23387
- https://github.com/rancher/rancher/security/advisories/GHSA-5qmp-9x47-92q8
nvd · CVE-2025-23387
- https://bugzilla.suse.com/show_bug.cgi?id=CVE-2025-23387
- https://github.com/rancher/rancher/security/advisories/GHSA-5qmp-9x47-92q8
osv · GHSA-5qmp-9x47-92q8
- https://github.com/rancher/rancher/security/advisories/GHSA-5qmp-9x47-92q8
- https://nvd.nist.gov/vuln/detail/CVE-2025-23387
- https://github.com/rancher/rancher/pull/48616
- https://github.com/rancher/rancher/pull/48998
- https://github.com/rancher/rancher/pull/48999
- https://github.com/rancher/rancher/pull/49000
- https://github.com/rancher/rancher/commit/2481630c4a5a75d81eb69d10d7558ea833395a1e
- https://github.com/rancher/rancher/commit/bedd911b9b321436faa2d9e20a161f6ac396aa74
- https://github.com/rancher/rancher/commit/ceeedb1aa67c319f4873615f19c3f56a66f39706
- https://github.com/rancher/rancher/commit/dfa034d05a55b5e57990a1f700176dcd8e963dbc
- https://bugzilla.suse.com/show_bug.cgi?id=CVE-2025-23387
- 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
osv · GO-2025-3489
Related changes
Linked by CVE identifierNo related changes are available here.