Answer in brief
CVE-2026-45726 records a High severity vulnerability in Omni: Reader-level users can retrieve imported cluster CA keys via ResourceService. The current sources do not mark it as known exploited. The current feed maps siderolabs/omni (generic), github.com/siderolabs/omni (go), github.com/siderolabs/omni (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps siderolabs/omni (generic), github.com/siderolabs/omni (go), github.com/siderolabs/omni (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| siderolabs/omnigeneric | >= 1.3.0, < 1.6.6 | Not reported |
| github.com/siderolabs/omnigo | >=1.3.0,<1.6.6 | 1.6.6 |
| github.com/siderolabs/omnigo | >=1.7.0,<1.7.3 | 1.7.3 |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 11, 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 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.
Quoted source text, attributed separately from HOL analysis.