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.
CVE-2026-45723
LOWPre-NVD 2.72.7—
EchelonGraph scoreMEDIUM confidence
This low-severity CVE scores 2.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 67% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
2.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.7Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 2.7
- EG Score
- 2.7(medium)
- EG Risk
- 12(Track)EG Risk 12/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity27% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 33%
- KEV
- Not listed
Published
June 5, 2026
Last Modified
September 18, 2026
References (7)
- security-advisories@githubhttps://github.com/siderolabs/omni/commit/13c3f289789842e1fd954d98babb34b94eea1192
- security-advisories@githubhttps://github.com/siderolabs/omni/commit/3e69e80802624bf322f16aa499d5eafca16d0025
- security-advisories@githubhttps://github.com/siderolabs/omni/commit/9426c2cabccaa1d442bc8ebf28c16cae2d7c6ff7
- security-advisories@githubhttps://github.com/siderolabs/omni/pull/2817
- security-advisories@githubhttps://github.com/siderolabs/omni/releases/tag/v1.6.6
- security-advisories@githubhttps://github.com/siderolabs/omni/releases/tag/v1.7.3
- security-advisories@githubhttps://github.com/siderolabs/omni/security/advisories/GHSA-c66c-vq6w-fvh5
Vendor Advisories for CVE-2026-45723(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/siderolabs/omni | — | 1.7.3 | — |
Weakness Classification(5)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 21:17 UTCEG score recompute
- 2026-09-18 20:36 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 20:18 UTCEG score recompute
- 2026-07-31 05:14 UTCEG score recompute
- 2026-07-26 21:55 UTCEG score recompute
- 2026-07-23 03:16 UTCEG score recompute
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-05 15:57 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-45723?
CVE-2026-45723 is a low vulnerability published on June 5, 2026. 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…
When was CVE-2026-45723 disclosed?
CVE-2026-45723 was first published in the National Vulnerability Database on June 5, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45723 actively exploited?
CVE-2026-45723 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 67.5% of all scored CVEs.
What is the CVSS score of CVE-2026-45723?
CVE-2026-45723 has a CVSS v3 base score of 2.7 (NVD).
How do I remediate CVE-2026-45723?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45723, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45723
Is Your Infrastructure Affected by CVE-2026-45723?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.