CVE-2026-45726: Omni: Reader-level users can retrieve imported cluster CA keys via ResourceService
Summary Omni supports importing standalone Talos clusters. During this process, an ImportedClusterSecrets resource is created, which contains the full CA secrets bundle for the cluster being imported. If these secrets are not rotated by the importing actor, an authenticated Omni user with Reader access can read this resource and gain full access to the Talos, Kubernetes and etcd APIs of the cluster.
Published Jun 5, 2026
Affected packages
github.com/siderolabs/omni
- Ecosystem
- Go
- Affected
- >= 1.3.0, < 1.6.6
- Fixed in
- 1.6.6
- Check
go list -m github.com/siderolabs/omni
github.com/siderolabs/omni
- Ecosystem
- Go
- Affected
- >= 1.7.0, < 1.7.3
- Fixed in
- 1.7.3
- Check
go list -m github.com/siderolabs/omni
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Omni supports importing standalone Talos clusters.
During this process, an ImportedClusterSecrets resource is created, which contains the full CA secrets bundle for the cluster being imported.
If these secrets are not rotated by the importing actor, an authenticated Omni user with Reader access can read this resource and gain full access to the Talos, Kubernetes and etcd APIs of the cluster.
Severity
- Attack Vector: Adjacent: the attacker needs to be in the same network to be able to access Talos/Kubernetes APIs with the compromised keys.
- Attack Complexity: High: the attacker needs a deep understanding of Omni's internals. The resource is only created for imported clusters, and is normally not represented to users via any high-level API.
- Privileges Required: Low: the role
Readeris sufficient for the attacker to be able to read an imported cluster's secrets. - User Interaction: Required: another user must have imported a cluster to Omni for this vulnerability to exist.
- Scope: Changed: the leaked CA private keys let an attacker directly get full control on Kubernetes or Talos, beyond the limitations enforced by Omni.
- Confidentiality Impact: High: full cluster CA private keys (Kubernetes, Talos, etcd, service account) are exposed.
- Integrity Impact: High: with the CA keys the attacker has full control on Kubernetes and Talos of the compromised (imported) cluster, and modify the workloads on it.
- Availability Impact: High: with the CA keys the attacker has full control on Kubernetes and Talos of the compromised (imported) cluster, and modify the workloads on it.
Impact
- Any Reader-level account can exfiltrate the complete CA private key hierarchy (Kubernetes CA, etcd CA, service account key) of the imported clusters whose secrets are not yet rotated ("tainted" imported clusters).
- With the Kubernetes CA private key, an attacker can sign certificates for any Kubernetes user or group, including
system:masters, achieving cluster-admin access to the imported cluster entirely outside Omni's control plane. - Impact scope extends beyond Omni to every Kubernetes workload, credential, and secret stored in the affected imported cluster.
Credit
This vulnerability was discovered and reported by bugbunny.ai.
Credited to bugbunny-research.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-45720
Omni has a TOCTOU race condition that allows multiple concurrent uses of a single-use SAML session token
high7.0Jun 5, 2026CVE-2026-45723
Omni: Operator can traverse image-factory API paths via unsanitized `talos_version` in CreateSchematic
low2.7Jun 5, 2026CVE-2025-59836
Omni is Vulnerable to DoS via Empty Create/Update Resource Requests
medium5.3Oct 13, 2025CVE-2025-61688
Omni vulnerable to information leak via API
high8.6Oct 13, 2025CVE-2025-59824
Omni Wireguard SideroLink potential escape
low0.5Sep 24, 2025
