CVE-2026-55998

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (25th 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
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.3Exploit: None knownExposed services: Not assessed

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

The endpoint /v3/import/{token}_{clusterId}.yaml retrieves the cluster object before validating the token. When a valid cluster ID references a cluster that has private registry secrets configured, a nil pointer dereference in pkg/systemtemplate/private_registry.go causes the request to return HTTP 502 Bad Gateway. For cluster IDs that do not exist, the endpoint returns HTTP 200. This observable difference in response codes constitutes a reliable enumeration oracle.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
39
EG Risk 39/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
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend 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 at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
25th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend 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 at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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)

Cluster Existence Oracle via Unauthenticated Import Endpoint · Advisory · rancher/rancher · GitHub

https://github.com/rancher/rancher/security/advisories/GHSA-23h9-rr79-r3gh
generic

Making sure you're not a bot!

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 44× 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.

Showing the most recent 100 of 110 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:13 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 23:39 UTCEG score recompute
  5. 2026-10-06 15:18 UTCEPSS rescore
  6. 2026-10-05 19:37 UTCEG score recompute
  7. 2026-10-05 17:43 UTCEPSS rescore
  8. 2026-10-04 23:22 UTCEPSS rescore
  9. 2026-10-04 06:03 UTCEG score recompute
  10. 2026-10-03 14:26 UTCEPSS rescore
  11. 2026-10-02 17:56 UTCEPSS rescore
  12. 2026-10-02 10:00 UTCEG score recompute
  13. 2026-10-01 19:50 UTCEPSS rescore
  14. 2026-10-01 02:21 UTCEG score recompute
  15. 2026-09-30 15:03 UTCEPSS rescore
  16. 2026-09-29 15:22 UTCEPSS rescore
  17. 2026-09-29 06:20 UTCEG score recompute
  18. 2026-09-28 13:51 UTCEPSS rescore
  19. 2026-09-27 17:45 UTCEG score recompute
  20. 2026-09-27 13:48 UTCEPSS rescore
  21. 2026-09-26 15:59 UTCEPSS rescore
  22. 2026-09-25 04:35 UTCEG score recompute
  23. 2026-09-24 14:04 UTCEPSS rescore
  24. 2026-09-24 00:16 UTCEG score recompute
  25. 2026-09-23 17:54 UTCEPSS rescore
Show 75 more
  1. 2026-09-23 00:54 UTCEG score recompute
  2. 2026-09-22 01:53 UTCEG score recompute
  3. 2026-09-20 20:16 UTCEPSS rescore
  4. 2026-09-19 23:25 UTCEG score recompute
  5. 2026-09-19 00:23 UTCEG score recompute
  6. 2026-09-18 19:28 UTCEPSS rescore
  7. 2026-09-18 01:22 UTCEG score recompute
  8. 2026-09-17 19:31 UTCEPSS rescore
  9. 2026-09-17 02:20 UTCEG score recompute
  10. 2026-09-16 14:08 UTCEPSS rescore
  11. 2026-09-16 05:15 UTCEPSS rescore
  12. 2026-09-16 03:16 UTCEG score recompute
  13. 2026-09-15 03:11 UTCEPSS rescore
  14. 2026-09-14 01:52 UTCEG score recompute
  15. 2026-09-13 16:47 UTCEPSS rescore
  16. 2026-09-13 02:51 UTCEG score recompute
  17. 2026-09-12 03:49 UTCEG score recompute
  18. 2026-09-11 14:53 UTCEPSS rescore
  19. 2026-09-11 04:46 UTCEG score recompute
  20. 2026-09-10 09:35 UTCEPSS rescore
  21. 2026-09-09 06:26 UTCEG score recompute
  22. 2026-09-08 22:01 UTCEPSS rescore
  23. 2026-09-07 18:22 UTCEG score recompute
  24. 2026-09-07 16:01 UTCEPSS rescore
  25. 2026-09-06 13:47 UTCEPSS rescore
  26. 2026-09-06 07:43 UTCEG score recompute
  27. 2026-09-05 08:41 UTCEG score recompute
  28. 2026-09-04 09:39 UTCEG score recompute
  29. 2026-09-04 05:07 UTCEPSS rescore
  30. 2026-09-03 07:01 UTCEG score recompute
  31. 2026-09-02 14:12 UTCEPSS rescore
  32. 2026-09-01 21:05 UTCEG score recompute
  33. 2026-09-01 13:54 UTCEPSS rescore
  34. 2026-09-01 04:40 UTCEPSS rescore
  35. 2026-08-30 20:32 UTCEG score recompute
  36. 2026-08-30 19:17 UTCEPSS rescore
  37. 2026-08-30 01:22 UTCEPSS rescore
  38. 2026-08-29 21:30 UTCEG score recompute
  39. 2026-08-28 21:41 UTCEPSS rescore
  40. 2026-08-27 19:56 UTCEG score recompute
  41. 2026-08-27 14:25 UTCEPSS rescore
  42. 2026-08-26 19:07 UTCEG score recompute
  43. 2026-08-26 14:46 UTCEPSS rescore
  44. 2026-08-25 18:12 UTCEG score recompute
  45. 2026-08-25 13:49 UTCEPSS rescore
  46. 2026-08-24 19:07 UTCEG score recompute
  47. 2026-08-23 20:03 UTCEG score recompute
  48. 2026-08-23 00:19 UTCEPSS rescore
  49. 2026-08-22 21:01 UTCEG score recompute
  50. 2026-08-21 23:49 UTCEPSS rescore
  51. 2026-08-20 22:57 UTCEG score recompute
  52. 2026-08-20 22:55 UTCEPSS rescore
  53. 2026-08-19 23:56 UTCEG score recompute
  54. 2026-08-19 17:04 UTCEPSS rescore
  55. 2026-08-19 00:54 UTCEG score recompute
  56. 2026-08-18 13:48 UTCEPSS rescore
  57. 2026-08-18 01:52 UTCEG score recompute
  58. 2026-08-17 13:47 UTCEPSS rescore
  59. 2026-08-17 02:50 UTCEG score recompute
  60. 2026-08-16 14:56 UTCEPSS rescore
  61. 2026-08-16 03:48 UTCEG score recompute
  62. 2026-08-16 02:14 UTCEPSS rescore
  63. 2026-08-15 04:46 UTCEG score recompute
  64. 2026-08-15 01:30 UTCEPSS rescore
  65. 2026-08-14 05:44 UTCEG score recompute
  66. 2026-08-13 22:00 UTCEPSS rescore
  67. 2026-08-13 06:42 UTCEG score recompute
  68. 2026-08-12 13:51 UTCEPSS rescore
  69. 2026-08-12 07:41 UTCEG score recompute
  70. 2026-08-11 08:39 UTCEG score recompute
  71. 2026-08-11 00:00 UTCEPSS rescore
  72. 2026-08-10 09:37 UTCEG score recompute
  73. 2026-08-09 13:46 UTCEPSS rescore
  74. 2026-08-09 10:36 UTCEG score recompute
  75. 2026-08-08 16:37 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55998?
CVE-2026-55998 is a medium vulnerability published on August 5, 2026. The endpoint /v3/import/{token}{clusterId}.yaml retrieves the cluster object before validating the token. When a valid cluster ID references a cluster that has private registry secrets configured, a nil pointer dereference in pkg/systemtemplate/privateregistry.go causes the request to return HTTP…
When was CVE-2026-55998 disclosed?
CVE-2026-55998 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-55998 actively exploited?
CVE-2026-55998 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55998?
CVE-2026-55998 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55998?
No fix for CVE-2026-55998 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-55998

Explore →

Is Your Infrastructure Affected by CVE-2026-55998?

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

Book a Demo →Browse All CVEs