CVE-2026-45726

HIGHPre-NVD 7.67.6
EchelonGraph scoreLOW confidence

This high-severity CVE scores 7.6 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.0%, top 96% 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: cna:github_m, epss
7.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.6Exploit: NoneExposed: 0

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

Omni: Reader-level users can retrieve imported cluster CA keys via ResourceService

Summary

Omni supports importing standalone Talos clusters.

During this process, an ImportedClusterSecrets resource is created, which contains the full CA secrets bundle for the cluster being imported.

If these secrets are not rotated by the importing actor, an authenticated Omni user with Reader access can read this resource and gain full access to the Talos, Kubernetes and etcd APIs of the cluster.

Severity

  • Attack Vector: Adjacent: the attacker needs to be in the same network to be able to access Talos/Kubernetes APIs with the compromised keys.
  • Attack Complexity: High: the attacker needs a deep understanding of Omni's internals. The resource is only created for imported clusters, and is normally not represented to users via any high-level API.
  • Privileges Required: Low: the role Reader is sufficient for the attacker to be able to read an imported cluster's secrets.
  • User Interaction: Required: another user must have imported a cluster to Omni for this vulnerability to exist.
  • Scope: Changed: the leaked CA private keys let an attacker directly get full control on Kubernetes or Talos, beyond the limitations enforced by Omni.
  • Confidentiality Impact: High: full cluster CA private keys (Kubernetes, Talos, etcd, service account) are exposed.
  • Integrity Impact: High: with the CA keys the attacker has full control on Kubernetes and Talos of the compromised (imported) cluster, and modify the workloads on it.
  • Availability Impact: High: with the CA keys the attacker has full control on Kubernetes and Talos of the compromised (imported) cluster, and modify the workloads on it.

Impact

  • Any Reader-level account can exfiltrate the complete CA private key hierarchy (Kubernetes CA, etcd CA, service account key) of the imported clusters whose secrets are not yet rotated ("tainted" imported clusters).
  • With the Kubernetes CA private key, an attacker can sign certificates for any Kubernetes user or group, including system:masters, achieving cluster-admin access to the imported cluster entirely outside Omni's control plane.
  • Impact scope extends beyond Omni to every Kubernetes workload, credential, and secret stored in the affected imported cluster.

Credit

This vulnerability was discovered and reported by bugbunny.ai.

CVSS v3
7.6
EG Score
7.6(low)
EPSS
4.2%
KEV
Not listed

Published

June 5, 2026

Last Modified

June 5, 2026

Vendor Advisories for CVE-2026-45726(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/siderolabs/omni—1.7.3—

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-45726?
CVE-2026-45726 is a high vulnerability published on June 5, 2026. Omni: Reader-level users can retrieve imported cluster CA keys via ResourceService Summary Omni supports importing standalone Talos clusters. During this process, an ImportedClusterSecrets resource is created, which contains the full CA secrets bundle for the cluster being imported. If these…
When was CVE-2026-45726 disclosed?
CVE-2026-45726 was first published in the National Vulnerability Database on June 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45726 actively exploited?
CVE-2026-45726 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-45726?
CVE-2026-45726 has a CVSS v4.0 base score of 7.6 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-45726?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45726, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45726

Explore →

Is Your Infrastructure Affected by CVE-2026-45726?

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

Start Free Scan →Browse All CVEs