CVE-2026-45726

High

Description

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.

SeverityHigh
CVSS7.6
Exploit probability—
ProductGithub.com/siderolabs/omni
PublishedSep 17, 2026
First seenSep 17, 2026

How to fix

Update
  • github.com/siderolabs/omni1.6.6, 1.7.3 or later

Affected products

ProductAffected versionsFixed in
github.com/siderolabs/omniGo1.3.0 ≤ v < 1.6.6, 1.7.0 ≤ v < 1.7.31.6.6, 1.7.3

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.