CVE-2025-23387
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis vulnerability in SUSE Rancher allows unauthenticated (unauthorized) users to access an API endpoint that lists all CLI authentication tokens and enables their deletion. This exposes sensitive token information and permits attackers to delete tokens before legitimate CLI clients can use them, effectively causing a denial-of-service for CLI authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed Rancher versionRun 'kubectl get rancher -n cattle-system -o jsonpath='{.items[0].status.rancherVersion}'' or access Rancher UI > About RancherAffected if Version is 2.8.0 through 2.8.12, 2.9.0 through 2.9.6, or 2.10.0 through 2.10.2
-
Identify API ingress logsCheck Rancher API access logs or cluster ingress/controller logs for requests to /v3/tokens endpointAffected if GET or DELETE requests to token API paths originate from unauthenticated IP addresses or lack valid authentication headers
-
Audit token existenceQuery Rancher API with admin credentials: curl -sk -H "Authorization: Bearer $TOKEN" https://rancher-url/v3/tokens to list current tokensAffected if Unexpected tokens appear in the list or tokens are missing unexpectedly indicating prior unauthorized deletion
Environment is affected if Rancher version falls within 2.8.x before 2.8.13, 2.9.x before 2.9.7, or 2.10.x before 2.10.3 and unauthorized access to token endpoints is observed or possible
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Rancher to version 2.8.13, 2.9.7, or 2.10.3 or later. Until upgraded, monitor API access logs for unauthorized requests to token endpoints.
Rancher 2.8.13, 2.9.7, or 2.10.3 (depending on your current version branch)
- Identify current Rancher version by checking the Rancher UI or using kubectl get rancher
- For Rancher 2.8.x: Upgrade to version 2.8.13 or later
- For Rancher 2.9.x: Upgrade to version 2.9.7 or later
- For Rancher 2.10.x: Upgrade to version 2.10.3 or later
- Follow standard SUSE Rancher upgrade procedures: create backup, test in staging environment, then apply to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23387 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-23387 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data