# CVE-2026-45723: Omni: Operator can traverse image-factory API paths via unsanitized `talos_version` in CreateSchematic

> An authenticated operator can exploit unsanitized input to probe internal endpoints on the image-factory host, potentially disclosing diagnostic information.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-c66c-vq6w-fvh5, GO-2026-5316

## What is CVE-2026-45723?

CVE-2026-45723 is a low-severity server-side request forgery vulnerability in siderolabs omni, published on 17 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Omni manages Kubernetes on bare metal, virtual machines, or in a cloud. Prior to 1.6.6 and 1.7.3, managementServer.CreateSchematic in internal/backend/grpc/schematics.go passes the caller-controlled TalosVersion field to imageFactoryClient.OverlaysVersions without validating it as a version. An authenticated Operator can submit traversal segments in TalosVersion, and url.URL.JoinPath normalizes them into unintended paths on the configured image-factory host. Omni then issues HTTP GET requests to those paths and reflects error-body content, enabling same-host endpoint probing and possible disclosure of internal diagnostics while preventing redirection to another host or write requests. This issue is fixed in versions 1.6.6 and 1.7.3.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-441 (Unintended Proxy or Intermediary), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-209 (Generation of Error Message Containing Sensitive Information), CWE-20 (Improper Input Validation)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/siderolabs/omni` | Go | All versions | 1.6.6, 1.7.3 |
| `github.com/siderolabs/omni` | Go | All versions | 1.6.6 |
| `github.com/siderolabs/omni` | Go | All versions | 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-45723?

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

## Is CVE-2026-45723 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45723 is a low-severity server-side request forgery vulnerability in siderolabs omni, published on 17 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-45723 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/siderolabs/omni (Go): affected all versions; fixed in 1.6.6, 1.7.3
- github.com/siderolabs/omni (Go): affected all versions; fixed in 1.6.6
- github.com/siderolabs/omni (Go): affected all versions; 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-45723/ (Markdown: https://insights.sbomify.com/CVE-2026-45723/index.md)
```

## Sources

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

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