Omni Wireguard SideroLink potential escape

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

0.5 · 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 · score source

EPSS

• CVE-2025-59824: 0.21% estimated exploitation activity in the next 30 days; percentile 10.55 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Overview Omni and each Talos machine establish a peer-to-peer (P2P) SideroLink connection using WireGuard to mutually authenticate and authorize access. In this setup, Omni assigns a random IPv6 address to each Talos machine from a /64 network block. Omni itself uses the fixed ::1 address within that same block. From Omni's perspective, this is a WireGuard interface with multiple peers, where each peer corresponds to a Talos machine. 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. --- Impact This…

Published by the source

24 Sep 2025, 18:57 UTC

Last modified by the source

23 Oct 2025, 20:12 UTC

Source last checked

26 Oct 2026, 15:13 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-hqrf-67pm-wgfq

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-59824

Advisory: Omni Wireguard SideroLink potential escape
IDs: CVE-2025-59824, GHSA-hqrf-67pm-wgfq
Record: https://patchnext.com/advisories/cve-2025-59824 (revision 1, source checked 26 Oct 2026, 15:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 0.5)
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 0.48.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siderolabs/omni: affected < 0.48.0; fixed in 0.48.0

## 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-hqrf-67pm-wgfq (GitHub-reviewed advisory GHSA-hqrf-67pm-wgfq lists affected ranges: Go github.com/siderolabs/omni >=0 <0.48.0)

Commands are suggestions: review each one before running it.