Approved changes feed: RSS · Atom
cpe:2.3:a:siderolabs:omni:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Siderolabs (7bc67f54-50f2-5412-9a61-fd541f7c961c) |
|---|---|
| Product | Omni (364da6b4-f4d5-5f94-9868-45d6e177716f) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/siderolabs/omni-client |
purl2cpe | 2026-06-01 10:18:03.774675 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-45720 |
vulnerable | 2026-10-13 12:29:45.343032 |
Omni: TOCTOU race condition allows multiple concurrent uses of a single-use SAML session token
HIGH (7)
Omni manages Kubernetes on bare metal, virtual machines, or in a cloud. Prior to 1.6.6 and from 1.7.0 until 1.7.3, SAML.getSession in internal/pkg/auth/interceptor/saml.go checks SAMLAssertion.Used and marks it used in separate state operations. Concurrent requests carrying the same captured saml-session token can each observe the assertion as unused and obtain authentication as the victim before either update is visible. The attacker can invoke SAML-protected gRPC endpoints, use ConfirmPublicKey to create multiple persistent credentials tied to the victim, and generate audit entries attributed to the victim, with the resulting access potentially affecting confidentiality, integrity, and availability according to the victim's privileges. This issue is fixed in versions 1.6.6 and 1.7.3.
Published: 2026-09-17T19:40:57.112Z
Updated: 2026-09-17T20:21:50.874Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-45726 |
vulnerable | 2026-10-13 12:29:45.191765 |
Omni: Reader-level users can retrieve imported cluster CA keys via ResourceService
HIGH (7.6)
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.
Published: 2026-09-17T19:37:50.625Z
Updated: 2026-09-21T21:09:15.556Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-61688 |
vulnerable | 2026-06-08 07:37:27.932973 |
Omni leaks information via the API
HIGH (8.6)
Omni manages Kubernetes on bare metal, virtual machines, or in a cloud. Prior to 1.1.5 and 1.0.2, Omni might leak sensitive information via an API.
Published: 2025-10-13T20:46:54.907Z
Updated: 2025-10-14T14:14:06.042Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-59836 |
vulnerable | 2026-06-08 07:35:23.293013 |
Omni is Vulnerable to DoS via Empty Create/Update Resource Requests
MEDIUM (5.3)
Omni manages Kubernetes on bare metal, virtual machines, or in a cloud. Prior to 1.1.5 and 1.0.2, there is a nil pointer dereference vulnerability in the Omni Resource Service allows unauthenticated users to cause a server panic and denial of service by sending empty create/update resource requests through the API endpoints. The vulnerability exists in the isSensitiveSpec function which calls grpcomni.CreateResource without checking if the resource's metadata field is nil. When a resource is created with an empty Metadata field, the CreateResource function attempts to access resource.Metadata.Version causing a segmentation fault. This vulnerability is fixed in 1.1.5 and 1.0.2.
Published: 2025-10-13T20:43:40.844Z
Updated: 2025-10-14T14:28:17.108Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-59824 |
vulnerable | 2026-06-08 07:35:23.267777 |
Omni Wireguard SideroLink potential escape
Omni manages Kubernetes on bare metal, virtual machines, or in a cloud. Prior to version 0.48.0, Omni Wireguard SideroLink has the potential to escape. Omni and each Talos machine establish a peer-to-peer (P2P) SideroLink connection using WireGuard to mutually authenticate and authorize access. The WireGuard interface on Omni is configured to ensure that the source IP address of an incoming packet matches the IPv6 address assigned to the Talos peer. However, it performs no validation on the packet's destination address. The Talos end of the SideroLink connection cannot be considered a trusted environment. Workloads running on Kubernetes, especially those configured with host networking, could gain direct access to this link. Therefore, a malicious workload could theoretically send arbitrary packets over the SideroLink interface. This issue has been patched in version 0.48.0.
Published: 2025-09-24T19:48:23.935Z
Updated: 2025-09-24T20:09:36.681Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.