CVE-2026-45726

HIGHPre-NVD 7.67.6
EchelonGraph scoreLOW confidence

This high-severity CVE scores 7.6 under a secondary CVSS source (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: epss, secondary
7.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.6Exploit: None knownExposed: 0

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

Omni manages Kubernetes on bare metal, virtual machines, or in a cloud. From 1.3.0 until 1.6.6 and 1.7.3, importing a standalone Talos cluster creates an ImportedClusterSecrets resource containing the cluster's complete CA secrets bundle. The access rules in internal/backend/runtime/omni/state_access.go allow an authenticated user with the Reader role to retrieve the resource through ResourceService if the importing actor has not rotated those secrets, exposing Kubernetes, Talos, and etcd CA private keys plus the service-account key. The Kubernetes CA private key permits certificate signing for privileged identities such as system:masters and provides control of the imported cluster outside Omni's authorization boundary, including its workloads, credentials, and secrets. This issue is fixed in versions 1.6.6 and 1.7.3.

CVSS v3
7.6
EG Score
7.6(low)
EG Risk
39(Track)
EG Risk 39/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
Severity76% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

June 5, 2026

Last Modified

September 17, 2026

Advisory Details (7)

Auto-updated Sep 17, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

v1.7.3

Patch available: siderolabs/omni v1.7.3

https://github.com/siderolabs/omni/releases/tag/v1.7.3
github_release Patch Available

v1.6.6

Patch available: siderolabs/omni v1.6.6

https://github.com/siderolabs/omni/releases/tag/v1.6.6
github_commit

commit b8ca100c4539 (siderolabs/omni)

Fix landed in siderolabs/omni commit b8ca100c4539 — awaiting tagged release

https://github.com/siderolabs/omni/commit/b8ca100c4539ea83f0ac2e53dcd523e6e5b68111
github_commit

commit a224cb020f3a (siderolabs/omni)

Fix landed in siderolabs/omni commit a224cb020f3a — awaiting tagged release

https://github.com/siderolabs/omni/commit/a224cb020f3aaca2bc21c3e32a38eb4a37e531e8
github_commit

commit 25fa9e141ee0 (siderolabs/omni)

Fix landed in siderolabs/omni commit 25fa9e141ee0 — awaiting tagged release

https://github.com/siderolabs/omni/commit/25fa9e141ee00285e70210ed40d11e4e457c871d
github_pr

fix: change ImportedClusterSecrets access level to operator

Fix merged in siderolabs/omni PR #2807 on 2026-05-07 — awaiting tagged release

https://github.com/siderolabs/omni/pull/2807
github Patch Available

Reader-level users can retrieve imported cluster CA keys via ResourceService · Advisory · siderolabs/omni · GitHub

https://github.com/siderolabs/omni/security/advisories/GHSA-wv8c-6mx2-xf4j

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—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 2× in last 7d / 2× 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-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 20:18 UTCEG score recompute
  3. 2026-07-31 05:14 UTCEG score recompute
  4. 2026-07-26 21:55 UTCEG score recompute
  5. 2026-07-23 03:16 UTCEG score recompute
  6. 2026-06-14 23:18 UTCEPSS rescore
  7. 2026-06-13 23:00 UTCEPSS rescore
  8. 2026-06-12 23:12 UTCEPSS rescore
  9. 2026-06-05 15:57 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-45726?
CVE-2026-45726 is a high vulnerability published on June 5, 2026. Omni manages Kubernetes on bare metal, virtual machines, or in a cloud. From 1.3.0 until 1.6.6 and 1.7.3, importing a standalone Talos cluster creates an ImportedClusterSecrets resource containing the cluster's complete CA secrets bundle. The access rules in…
When was CVE-2026-45726 disclosed?
CVE-2026-45726 was first published in the National Vulnerability Database on June 5, 2026, with the most recent update on September 17, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 99.1% of all scored CVEs.
What is the CVSS score of CVE-2026-45726?
CVE-2026-45726 has a CVSS v3 base score of 7.6 (NVD). 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