Answer in brief
CVE-2026-45720 records a High severity vulnerability in Omni: TOCTOU race condition allows multiple concurrent uses of a single-use SAML session token. The current sources do not mark it as known exploited. The current feed maps siderolabs/omni (generic), github.com/siderolabs/omni (go), github.com/siderolabs/omni (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps siderolabs/omni (generic), github.com/siderolabs/omni (go), github.com/siderolabs/omni (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| siderolabs/omnigeneric | < 1.6.6 || >= 1.7.0, < 1.7.3 | Not reported |
| github.com/siderolabs/omnigo | <1.6.6 | 1.6.6 |
| github.com/siderolabs/omnigo | >=1.7.0,<1.7.3 | 1.7.3 |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 11, 2026
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.
Quoted source text, attributed separately from HOL analysis.