CVE-2026-55997

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 100% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

August 5, 2026

Last Modified

August 6, 2026

Advisory Details (2)

Auto-updated Aug 5, 2026
Patch available. Sources: github.
github Patch Available

Long-lived Rancher registration token exposed in plaintext · Advisory · rancher/rancher · GitHub

https://github.com/rancher/rancher/security/advisories/GHSA-7r53-jvhg-9jq4

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-25 13:59 UTCEG score recompute
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-25 02:06 UTCEG score recompute
  4. 2026-08-23 02:39 UTCEG score recompute
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-21 03:11 UTCEG score recompute
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-17 14:12 UTCEG score recompute
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-16 02:37 UTCEG score recompute
  11. 2026-08-16 02:14 UTCEPSS rescore
  12. 2026-08-15 02:54 UTCEG score recompute
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-12 15:36 UTCEG score recompute
  15. 2026-08-12 13:51 UTCEPSS rescore
  16. 2026-08-11 15:52 UTCEG score recompute
  17. 2026-08-08 16:43 UTCEG score recompute
  18. 2026-08-08 16:37 UTCEPSS rescore
  19. 2026-08-07 17:00 UTCEG score recompute
  20. 2026-08-06 17:17 UTCEG score recompute
  21. 2026-08-06 13:47 UTCEPSS rescore
  22. 2026-08-06 05:25 UTCEG score recompute
  23. 2026-08-06 04:25 UTCEG score recompute
  24. 2026-08-06 02:18 UTCEG score recompute
  25. 2026-08-05 19:17 UTCEPSS rescore
Show 5 more
  1. 2026-08-05 14:26 UTCEG score recompute
  2. 2026-08-05 13:47 UTCEG score recompute
  3. 2026-08-05 08:20 UTCEG score recompute
  4. 2026-08-05 08:12 UTCEG score recompute
  5. 2026-08-05 08:10 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-55997?
CVE-2026-55997 is a high vulnerability published on August 5, 2026. 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…
When was CVE-2026-55997 disclosed?
CVE-2026-55997 was first published in the National Vulnerability Database on August 5, 2026, with the most recent update on August 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55997 actively exploited?
CVE-2026-55997 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.8% of all scored CVEs.
What is the CVSS score of CVE-2026-55997?
CVE-2026-55997 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-55997?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55997, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-55997

Explore →

Is Your Infrastructure Affected by CVE-2026-55997?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.