CVE-2026-45726 json
Omni: Reader-level users can retrieve imported cluster CA keys via ResourceService
published 2026-06-05 5 mo ago modified 2026-09-24 45 d ago also EUVD-2026-82401 , GHSA-wv8c-6mx2-xf4j , GO-2026-5725
- cvss
- 7.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/siderolabs/omni 1.6.6, 1.7.3
- siderolabs omni 1.6.6
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 48 d ago
Exploit prediction
0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.6 | CVSS:3.1/AV:A/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H |
| GitHub | 3.1 | 7.6 | CVSS:3.1/AV:A/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/siderolabs/omni | >=1.3.0, <1.6.6 >=1.7.0, <1.7.3 |
1.6.6 1.7.3 |
Affected products
- siderolabs omni
Classification
References
- github.com /siderolabs/omni/pull/2807
- github.com /siderolabs/omni/commit/25fa9e141ee00285e70210ed40d11e4e457c871d
- github.com /siderolabs/omni/commit/a224cb020f3aaca2bc21c3e32a38eb4a37e531e8
- github.com /siderolabs/omni/commit/b8ca100c4539ea83f0ac2e53dcd523e6e5b68111
-
github.com
/siderolabs/omni/security/advisories/GHSA-wv8c-6mx2-xf4j
web, advisory
-
github.com
/siderolabs/omni/releases/tag/v1.6.6
web
-
github.com
/siderolabs/omni/releases/tag/v1.7.3
web
-
github.com
/siderolabs/omni
package
Sources
- CVE List CVE-2026-45726
- GitHub Advisory GHSA-wv8c-6mx2-xf4j
- NVD CVE-2026-45726
- OSV GO-2026-5725
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.