Skip to main content
VulnerabilityPublished

CVE-2026-45720: siderolabs omni · Authentication Bypass by Capture-replay

Affects siderolabs omniSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.0 High : upgrade to 1.7.3 or 1.6.6 soon.

Data as of 1 Nov 2026, 22:58 UTC

CVSS 3.1 base score
7.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.7.3, 1.6.6
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

What to do

Upgrade omni and siderolabs/omni to 1.7.3 or 1.6.6.

Affected software

ProductAffectedFixed in
siderolabsomniAffected
  • >=1.7.0 <1.7.3
Fixed in
  • 1.7.3
siderolabsomniAffected
  • <1.6.6
Fixed in
  • 1.6.6
GitHubsiderolabs/omnipkg:github/siderolabs/omniOther threatsAffected
  • <1.6.6
  • >=1.7.0 <1.7.3
Fixed in
  • 1.6.6
  • 1.7.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in siderolabs omni versions 1.6.6 and 1.7.3. Users should upgrade to at least version 1.6.6 or 1.7.3 to remediate this issue. No other mitigation or temporary workaround is indicated in the available data.

Description

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.

References

Community reviews

Loading reviews…