Description
Rancher issues long-lived registration tokens to authenticate nodes and agents joining a downstream cluster. These tokens were stored and exposed in plaintext with no expiration, so a malicious user could obtain one either through the Rancher API, etcd, stored automation, or direct file access on a node, and could use it at any time to register a rogue node into the cluster.
Published: 2026-08-05
Score: 8.8 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Rancher generates long‑lived registration tokens that authenticate nodes and agents joining downstream clusters. These tokens are stored in plaintext and have no expiration policy. Exposed tokens can be obtained through the Rancher API, etcd data, automation scripts, or direct file access on a node and can be used at any time to register a rogue node. This grants an attacker the privileges of a legitimate node, enabling the execution of workloads, exposure of cluster state, or lateral movement within the cluster. The flaw is a classic credential‑dumping issue, classified as CWE‑312, and does not require local system compromise once the token is acquired.

Affected Systems

Rancher Rancher is affected. No specific product version or release is listed in the CNA data; the flaw applies to the default token generation and storage logic within Rancher’s node registration system.

Risk and Exploitability

The vulnerability has a CVSS score of 8.8, indicating high severity. No EPSS score is available, and the flaw is not listed in the CISA KEV catalog, suggesting it may not be actively exploited in the wild yet. However, the long‑lived, plaintext nature of the tokens means an attacker who can read the token through the API, etcd, automation scripts, or node file access can immediately register a rogue node. The attack does not require privileged access beyond the normal API/etcd credentials and can be completed by anyone able to interact with the Rancher API or the node file system.

Generated by OpenCVE AI on August 5, 2026 at 09:27 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Rancher to a version that encrypts registration tokens and imposes an expiration policy
  • Restrict access to the Rancher API and etcd to privileged roles and enforce least‑privilege and network segmentation
  • Audit the cluster for unknown or unauthorized node registrations and revoke unused tokens promptly

Generated by OpenCVE AI on August 5, 2026 at 09:27 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 05 Aug 2026 09:45:00 +0000

Type Values Removed Values Added
First Time appeared Rancher
Rancher rancher
Vendors & Products Rancher
Rancher rancher

Wed, 05 Aug 2026 08:15:00 +0000

Type Values Removed Values Added
Description Rancher issues long-lived registration tokens to authenticate nodes and agents joining a downstream cluster. These tokens were stored and exposed in plaintext with no expiration, so a malicious user could obtain one either through the Rancher API, etcd, stored automation, or direct file access on a node, and could use it at any time to register a rogue node into the cluster.
Title Long-lived Rancher registration token exposed in plaintext
Weaknesses CWE-312
References
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H'}


cve-icon MITRE

Status: PUBLISHED

Assigner: suse

Published:

Updated: 2026-08-05T07:53:00.194Z

Reserved: 2026-06-18T09:26:55.987Z

Link: CVE-2026-55997

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-05T09:30:11Z

Weaknesses
  • CWE-312

    Cleartext Storage of Sensitive Information