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% (1st percentile of EPSS-scored CVEs). 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 mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 8.8Exploit: None knownExposed services: Not assessed

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

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.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 5, 2026

Last Modified

September 1, 2026

Advisory Details (2)

Auto-updated Aug 5, 2026
No fix on record yet. Sources: github.
githubMentions a patch (unverified)

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

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

Making sure you're not a bot!

https://bugzilla.suse.com/show_bug.cgi?id=CVE-2026-55997

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 39× 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-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:13 UTCEPSS rescore
  4. 2026-10-07 23:48 UTCEPSS rescore
  5. 2026-10-06 23:39 UTCEG score recompute
  6. 2026-10-06 15:18 UTCEPSS rescore
  7. 2026-10-05 19:37 UTCEG score recompute
  8. 2026-10-05 17:43 UTCEPSS rescore
  9. 2026-10-04 23:36 UTCEG score recompute
  10. 2026-10-04 23:22 UTCEPSS rescore
  11. 2026-10-04 06:03 UTCEG score recompute
  12. 2026-10-03 14:26 UTCEPSS rescore
  13. 2026-10-03 01:12 UTCEG score recompute
  14. 2026-10-02 17:56 UTCEPSS rescore
  15. 2026-10-02 10:00 UTCEG score recompute
  16. 2026-10-01 19:50 UTCEPSS rescore
  17. 2026-10-01 02:21 UTCEG score recompute
  18. 2026-09-30 15:03 UTCEPSS rescore
  19. 2026-09-29 15:22 UTCEPSS rescore
  20. 2026-09-29 06:20 UTCEG score recompute
  21. 2026-09-28 13:51 UTCEPSS rescore
  22. 2026-09-27 17:45 UTCEG score recompute
  23. 2026-09-27 13:48 UTCEPSS rescore
  24. 2026-09-25 04:35 UTCEG score recompute
  25. 2026-09-24 14:04 UTCEPSS rescore
Show 58 more
  1. 2026-09-24 02:27 UTCEG score recompute
  2. 2026-09-23 17:54 UTCEPSS rescore
  3. 2026-09-22 01:53 UTCEG score recompute
  4. 2026-09-19 23:18 UTCEG score recompute
  5. 2026-09-18 03:51 UTCEG score recompute
  6. 2026-09-17 19:31 UTCEPSS rescore
  7. 2026-09-17 01:08 UTCEG score recompute
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-13 19:30 UTCEG score recompute
  11. 2026-09-13 16:47 UTCEPSS rescore
  12. 2026-09-12 19:01 UTCEG score recompute
  13. 2026-09-11 19:18 UTCEG score recompute
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-10 19:07 UTCEG score recompute
  16. 2026-09-10 09:35 UTCEPSS rescore
  17. 2026-09-09 06:26 UTCEG score recompute
  18. 2026-09-08 22:01 UTCEPSS rescore
  19. 2026-09-05 18:28 UTCEG score recompute
  20. 2026-09-04 09:38 UTCEG score recompute
  21. 2026-09-04 05:07 UTCEPSS rescore
  22. 2026-09-01 20:41 UTCEG score recompute
  23. 2026-09-01 13:54 UTCEPSS rescore
  24. 2026-09-01 04:40 UTCEPSS rescore
  25. 2026-08-30 21:48 UTCEG score recompute
  26. 2026-08-30 19:17 UTCEPSS rescore
  27. 2026-08-29 21:30 UTCEG score recompute
  28. 2026-08-28 21:41 UTCEPSS rescore
  29. 2026-08-25 13:59 UTCEG score recompute
  30. 2026-08-25 13:49 UTCEPSS rescore
  31. 2026-08-25 02:06 UTCEG score recompute
  32. 2026-08-23 02:39 UTCEG score recompute
  33. 2026-08-23 00:19 UTCEPSS rescore
  34. 2026-08-21 03:11 UTCEG score recompute
  35. 2026-08-20 22:55 UTCEPSS rescore
  36. 2026-08-17 14:12 UTCEG score recompute
  37. 2026-08-17 13:47 UTCEPSS rescore
  38. 2026-08-16 02:37 UTCEG score recompute
  39. 2026-08-16 02:14 UTCEPSS rescore
  40. 2026-08-15 02:54 UTCEG score recompute
  41. 2026-08-15 01:30 UTCEPSS rescore
  42. 2026-08-12 15:36 UTCEG score recompute
  43. 2026-08-12 13:51 UTCEPSS rescore
  44. 2026-08-11 15:52 UTCEG score recompute
  45. 2026-08-08 16:43 UTCEG score recompute
  46. 2026-08-08 16:37 UTCEPSS rescore
  47. 2026-08-07 17:00 UTCEG score recompute
  48. 2026-08-06 17:17 UTCEG score recompute
  49. 2026-08-06 13:47 UTCEPSS rescore
  50. 2026-08-06 05:25 UTCEG score recompute
  51. 2026-08-06 04:25 UTCEG score recompute
  52. 2026-08-06 02:18 UTCEG score recompute
  53. 2026-08-05 19:17 UTCEPSS rescore
  54. 2026-08-05 14:26 UTCEG score recompute
  55. 2026-08-05 13:47 UTCEG score recompute
  56. 2026-08-05 08:20 UTCEG score recompute
  57. 2026-08-05 08:12 UTCEG score recompute
  58. 2026-08-05 08:10 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

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 on August 5, 2026, with the most recent update on September 1, 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.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55997?
CVE-2026-55997 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55997?
No fix for CVE-2026-55997 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

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.

Book a Demo →Browse All CVEs