Omni: Operator can traverse image-factory API paths via unsanitized talos_version in CreateSchematic
CVE-2026-45723GHSA-c66c-vq6w-fvh5
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/siderolabs/omni 1.7.3, 1.6.6), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- < 1.6.6>= 1.7.0, < 1.7.3
- Fixed in
- 1.6.6, 1.7.3
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-c66c-vq6w-fvh5 lists affected ranges: Go github.com/siderolabs/omni >=0 =1.7.0 <1.7.3
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 2.7 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
- EPSS
- CVE-2026-45723: 0.49% estimated exploitation activity in the next 30 days; percentile 42.46 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary managementServer.CreateSchematic (internal/backend/grpc/schematics.go) passes the caller-controlled TalosVersion field directly to imageFactoryClient.OverlaysVersions, which embeds it verbatim into a fmt.Sprintf("/version/%s/overlays/official", talosVersion) path template. url.URL.JoinPath resolves any ../ sequences in that path, allowing an authenticated Operator to rewrite the URL path and force Omni to issue HTTP GET requests to unintended paths on the configured image-factory server. Error body content from those unintended endpoints is returned to the caller. Severity - Attack Vector: Network: exploited via the gRPC CreateSchematic API endpoint. - Attack Complexity: Low: once the attacker holds an Operator credential and has identified a media ID with an overlay, exploitation is a single API call. - Privileges Required: High: role.Operator is required, which has administrative capabilities on Omni. - User Interaction: None. - Scope: Unchanged: the traversal is…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-c66c-vq6w-fvh5
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-45723 Advisory: Omni: Operator can traverse image-factory API paths via unsanitized `talos_version` in CreateSchematic IDs: CVE-2026-45723, GHSA-c66c-vq6w-fvh5 Record: https://patchnext.com/advisories/cve-2026-45723 (revision 1, source checked 26 Oct 2026, 15:23 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Low (CVSS 2.7) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/siderolabs/omni 1.7.3, 1.6.6. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/siderolabs/omni: affected < 1.6.6; >= 1.7.0, < 1.7.3; fixed in 1.6.6, 1.7.3 ## Suggested inspection (read-only) - Go github.com/siderolabs/omni: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/siderolabs/omni. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-c66c-vq6w-fvh5 (GitHub-reviewed advisory GHSA-c66c-vq6w-fvh5 lists affected ranges: Go github.com/siderolabs/omni >=0 =1.7.0 <1.7.3) Commands are suggestions: review each one before running it.
Loading voting…