CVE-2026-45726

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

State
Published
Severity
7.6 High
Published
Sep 17, 2026
Updated
Sep 21, 2026
Reserved
May 13, 2026

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.17.6 HighCVSS:3.1/AV:A/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:HGitHub_M

Weaknesses

  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-522 Insufficiently Protected Credentials
  • CWE-732 Incorrect Permission Assignment for Critical Resource

Affected Products

ProductVersions
omnisiderolabs
  • >= 1.3.0, < 1.6.6Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.