CVE-2026-55997: Long-lived Rancher registration token exposed in plaintext

Published Aug 5, 2026
·
Updated

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.

Affected Software

1 affected component
rancher

Event History

Aug 5, 2026
CVE Published
via MITRE·07:53 AM
Data Sourced
via MITRE·07:53 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:16 AM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-55997?

CVE-2026-55997 has a high severity rating of 8.8.

2

What vulnerabilities does CVE-2026-55997 reveal?

CVE-2026-55997 exposes long-lived Rancher registration tokens in plaintext, allowing malicious users to authenticate with nodes and agents.

3

How do I fix CVE-2026-55997?

To fix CVE-2026-55997, you should immediately rotate any exposed registration tokens and implement token expiration policies.

4

What are the risks associated with CVE-2026-55997?

The risks include unauthorized access to downstream clusters and potential compromise of sensitive resources due to exposed plaintext tokens.

5

How can attackers exploit CVE-2026-55997?

Attackers can exploit CVE-2026-55997 by accessing the plaintext registration tokens through the Rancher API, etcd, stored automation, or direct file access.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203