# CVE-2025-59824: Omni Wireguard SideroLink potential escape

> Malicious Kubernetes workloads can bypass destination address validation on the SideroLink interface to access the management network.

- **Severity:** Low 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`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2025
- **Updated:** 24 Sep 2025
- **Also known as:** GHSA-hqrf-67pm-wgfq, GO-2025-3979

## What is CVE-2025-59824?

CVE-2025-59824 is a low-severity missing authorization vulnerability in siderolabs omni, published on 24 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2025-59824?

3 open source packages ship an affected version, including github.com/siderolabs/omni. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/siderolabs/omni` | Go | All versions | 0.48.0 |
| `github.com/siderolabs/omni` | Go | All versions | 0.48.0 |
| `github.com/siderolabs/omni` | Go | All versions | 0.48.0 |

Products: Siderolabs Omni.

## How do I fix CVE-2025-59824?

Upgrade github.com/siderolabs/omni to 0.48.0 or later.

## Is CVE-2025-59824 being exploited?

There is no known exploitation of CVE-2025-59824 in the wild and no public exploit code.

## Other vulnerabilities in siderolabs omni

- [CVE-2025-61688](https://insights.sbomify.com/CVE-2025-61688/): Omni leaks information via the API (high 8.6)
- [CVE-2025-59836](https://insights.sbomify.com/CVE-2025-59836/): Omni is Vulnerable to DoS via Empty Create/Update Resource Requests (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59824 and fix it if it is affected.

What it is: CVE-2025-59824 is a low-severity missing authorization vulnerability in siderolabs omni, published on 24 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59824 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/siderolabs/omni (Go): affected all versions; fixed in 0.48.0
- github.com/siderolabs/omni (Go): affected all versions; fixed in 0.48.0
- github.com/siderolabs/omni (Go): affected all versions; fixed in 0.48.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-59824/ (Markdown: https://insights.sbomify.com/CVE-2025-59824/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59824
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59824
- OSV: https://osv.dev/vulnerability/CVE-2025-59824

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-59824/
Summaries are generated and may contain mistakes; the official description above is the record.