# CVE-2025-59836: Omni is Vulnerable to DoS via Empty Create/Update Resource Requests

> Unauthenticated attackers can cause a server panic and denial of service by sending empty resource requests to the Omni API.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Oct 2025
- **Updated:** 14 Oct 2025
- **Also known as:** GHSA-4p3p-cr38-v5xp, GO-2025-4021

## What is CVE-2025-59836?

CVE-2025-59836 is a medium-severity vulnerability in siderolabs omni, published on 13 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Omni manages Kubernetes on bare metal, virtual machines, or in a cloud. Prior to 1.1.5 and 1.0.2, there is a nil pointer dereference vulnerability in the Omni Resource Service allows unauthenticated users to cause a server panic and denial of service by sending empty create/update resource requests through the API endpoints. The vulnerability exists in the isSensitiveSpec function which calls grpcomni.CreateResource without checking if the resource's metadata field is nil. When a resource is created with an empty Metadata field, the CreateResource function attempts to access resource.Metadata.Version causing a segmentation fault. This vulnerability is fixed in 1.1.5 and 1.0.2.

Weakness: CWE-703 (Improper Check or Handling of Exceptional Conditions), CWE-476 (NULL Pointer Dereference)

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

5 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 | 1.0.2, 1.1.5 |
| `github.com/siderolabs/omni` | Go | All versions | 1.0.2 |
| `github.com/siderolabs/omni` | Go | All versions | 1.0.2 |
| `github.com/siderolabs/omni` | Go | From 1.1.0-beta.0 | 1.1.5 |
| `github.com/siderolabs/omni` | Go | From 1.1.0-beta.0 | 1.1.5 |

Products: Siderolabs Omni.

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

Upgrade github.com/siderolabs/omni to a fixed version for your release line: 1.0.2 or 1.1.5.

## Is CVE-2025-59836 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59836 exists.

## 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-59824](https://insights.sbomify.com/CVE-2025-59824/): Omni Wireguard SideroLink potential escape (low 0.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59836 is a medium-severity vulnerability in siderolabs omni, published on 13 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59836 exists.

Affected packages and fixed versions:
- github.com/siderolabs/omni (Go): affected all versions; fixed in 1.0.2, 1.1.5
- github.com/siderolabs/omni (Go): affected all versions; fixed in 1.0.2
- github.com/siderolabs/omni (Go): affected all versions; fixed in 1.0.2
- github.com/siderolabs/omni (Go): affected from 1.1.0-beta.0; fixed in 1.1.5
- github.com/siderolabs/omni (Go): affected from 1.1.0-beta.0; fixed in 1.1.5

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-59836/ (Markdown: https://insights.sbomify.com/CVE-2025-59836/index.md)
```

## Sources

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

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