Skip to main content
CVE-2025-59824VulnerabilityPublished

CVE-2025-59824: siderolabs omni · Incorrect Authorization

Affects siderolabs omniSource CVE Database V5

0

Not known to be exploited · CVSS 0.5 Low : upgrade to 0.48.0 when convenient.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score
0.5Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.48.0
CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:U

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-26.

What to do

Upgrade siderolabs omni to 0.48.0.

Affected software

ProductAffectedFixed in
siderolabs omniAffected
  • <0.48.0
Fixed in
  • 0.48.0

AI-suggested

European organizations should immediately upgrade Omni to version 0.48.0 or later to apply the official patch that addresses this authorization flaw. Additionally, organizations should audit Kubernetes workloads to minimize the use of host networking unless strictly necessary, as this configuration increases exposure to the vulnerability. Implement strict network segmentation and access controls to limit which workloads can communicate over the SideroLink interface. Employ runtime security tools to monitor and detect anomalous network traffic originating from containers or workloads with elevated privileges. Regularly review and harden WireGuard configurations to ensure proper validation of both source and destination addresses. Finally, incorporate this vulnerability into vulnerability management and incident response plans to ensure rapid detection and remediation if exploitation attempts occur.

Description

Omni manages Kubernetes on bare metal, virtual machines, or in a cloud. Prior to version 0.48.0, Omni Wireguard SideroLink has the potential to escape. Omni and each Talos machine establish a peer-to-peer (P2P) SideroLink connection using WireGuard to mutually authenticate and authorize access. The WireGuard interface on Omni is configured to ensure that the source IP address of an incoming packet matches the IPv6 address assigned to the Talos peer. However, it performs no validation on the packet's destination address. The Talos end of the SideroLink connection cannot be considered a trusted environment. Workloads running on Kubernetes, especially those configured with host networking, could gain direct access to this link. Therefore, a malicious workload could theoretically send arbitrary packets over the SideroLink interface. This issue has been patched in version 0.48.0.

References

Community reviews

Loading reviews…