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

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

- **Severity:** High 7.6 (`CVSS:3.1/AV:A/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H`)
- **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:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-wv8c-6mx2-xf4j, GO-2026-5725

## 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 (Incorrect Permission Assignment for Critical Resource), CWE-522 (Insufficiently Protected Credentials), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-45726?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/siderolabs/omni` | Go | From 1.3.0 | 1.6.6, 1.7.3 |
| `github.com/siderolabs/omni` | Go | From 1.3.0 | 1.6.6 |
| `github.com/siderolabs/omni` | Go | From 1.3.0 | 1.6.6 |
| `github.com/siderolabs/omni` | Go | From 1.7.0 | 1.7.3 |
| `github.com/siderolabs/omni` | Go | From 1.7.0 | 1.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.

## Is CVE-2026-45726 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45726 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-45726 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/siderolabs/omni (Go): affected from 1.3.0; fixed in 1.6.6, 1.7.3
- github.com/siderolabs/omni (Go): affected from 1.3.0; fixed in 1.6.6
- github.com/siderolabs/omni (Go): affected from 1.3.0; fixed in 1.6.6
- github.com/siderolabs/omni (Go): affected from 1.7.0; fixed in 1.7.3
- github.com/siderolabs/omni (Go): affected from 1.7.0; fixed in 1.7.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-45726/ (Markdown: https://insights.sbomify.com/CVE-2026-45726/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45726
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45726
- OSV: https://osv.dev/vulnerability/CVE-2026-45726

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-45726/
Summaries are generated and may contain mistakes; the official description above is the record.