CVE-2026-45726 Omni: Reader-level users can retrieve imported cluster CA keys via ResourceService

High 7.6 Published Updated

Reader-level users can retrieve imported cluster CA keys, enabling full control over the Kubernetes cluster and bypassing authorization boundaries.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2026-45726?

CVE-2026-45726 is a high-severity missing authorization vulnerability in siderolabs omni, published on 17 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

Official 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.

Weakness: CWE-732, CWE-522, CWE-200

Which versions are affected by CVE-2026-45726?

5 open source packages ship an affected version, including github.com/siderolabs/omni.

PackageAffectedFixed in
github.com/siderolabs/omni GoFrom 1.3.01.6.6, 1.7.3
github.com/siderolabs/omni GoFrom 1.3.01.6.6
github.com/siderolabs/omni GoFrom 1.3.01.6.6
github.com/siderolabs/omni GoFrom 1.7.01.7.3
github.com/siderolabs/omni GoFrom 1.7.01.7.3

How do I fix CVE-2026-45726?

Upgrade github.com/siderolabs/omni to a fixed version for your release line: 1.6.6 or 1.7.3.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-45726 being exploited?

There is no known exploitation of CVE-2026-45726 in the wild and no public exploit code.

Sources

Also known as GHSA-wv8c-6mx2-xf4j, GO-2026-5725.

Is CVE-2026-45726 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free