CVE-2026-45726

HIGHPre-NVD 7.67.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (3rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-82401 (ENISA EUVD) · GHSA-wv8c-6mx2-xf4j (GitHub Security Advisories)Source: ENISA EUVD

7.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.6HIGHmedium confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity76% × 45%
Impact severity (EG Severity): CVSS 7.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.6): severity, escalated by confirmed exploitation. This CVE's 7.6 is its impact severity (EG Severity), not escalated.

EG Severity
7.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 5, 2026

Last Modified

September 24, 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 pull request

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 advisoryMentions a patch (unverified)

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 rangeFix by version rangeDependents
github.com/siderolabs/omni—
  • 1.3.0 up to 1.6.6: fixed in 1.6.6
  • 1.7.0 up to 1.7.3: fixed in 1.7.3
—

Weakness Classification(3)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  4. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  5. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  6. 2026-10-25 14:26 UTCEG score recompute
  7. 2026-10-24 21:02 UTCEG score recompute
  8. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  9. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  12. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-10-18 03:37 UTCEG score recompute
  16. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-10-17 13:36 UTCEG score recompute
  18. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-10-16 15:54 UTCOSV refresh
  20. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-10-12 16:04 UTCEG score recompute
  25. 2026-10-11 19:46 UTCEG score recompute
Show 26 more
  1. 2026-10-11 17:00 UTCEG score recompute
  2. 2026-10-11 14:26 UTCEG score recompute
  3. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  4. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  5. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  7. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-09-24 21:35 UTCEG score recompute
  17. 2026-09-21 21:17 UTCEG score recompute
  18. 2026-09-18 19:28 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  19. 2026-09-17 20:18 UTCEG score recompute
  20. 2026-07-31 05:14 UTCEG score recompute
  21. 2026-07-26 21:55 UTCEG score recompute
  22. 2026-07-23 03:16 UTCEG score recompute
  23. 2026-06-14 23:18 UTCEPSS rescoreEPSS <0.1% · 4th percentile
  24. 2026-06-13 23:00 UTCEPSS rescoreEPSS <0.1% · 4th percentile
  25. 2026-06-12 23:12 UTCEPSS rescoreEPSS <0.1% · 4th percentile
  26. 2026-06-05 15:57 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-45726?
CVE-2026-45726 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-45726 published?
The CVE record for CVE-2026-45726 was published on June 5, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-45726 actively exploited?
CVE-2026-45726 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-45726?
CVE-2026-45726 has a CVSS base score of 7.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-45726?
A fix for CVE-2026-45726 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-45726 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs