Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2025-59836: Omni manages Kubernetes on bare metal, virtual machines, or in a cloud

45
This week
MEDIUM 5.3REMOTEWATCHLISTUPGRADE

CVE-2025-59836 is a medium-severity flaw (CVSS 5.3) affecting omni. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 resour

Why this priority

  • Public exploit reference
  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score5.3 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.6% (top 52%)
CISA exploited listNo
WeaknessCWE-476, CWE-703
Published2025-10-13
Last modified2026-10-08
Publisher (CNA): GitHub, Inc. · Vendor: siderolabs

Share: LinkedIn · X · Reddit

Last updated 2026-10-08 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

siderolabs omni UPGRADE
Affected: < 1.0.2 · >= 1.1.0 and < 1.1.5
Fixed in: 1.0.2, 1.1.5
Safe to downgrade to: a release before 1.1.0
1. Check installed version
apt-cache policy omni || rpm -q omni || omni --version
2. UPGRADE to 1.0.2 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade omni
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade omni
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.1.0 (Debian / Ubuntu)
apt-cache madison omni sudo apt install omni=<VERSION_BEFORE_1.1.0> sudo apt-mark hold omni
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list omni sudo dnf downgrade omni-<VERSION_BEFORE_1.1.0> sudo dnf versionlock add omni
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-59836?

omni: upgrade to 1.0.2, 1.1.5. Exact commands for each OS are on this page.

Is CVE-2025-59836 being exploited?

CVE-2025-59836 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-59836 affect?

CVE-2025-59836 affects omni. Severity is medium (CVSS 5.3). 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

How urgent is CVE-2025-59836?

Priority 45/100. Public exploit reference; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Kubernetes vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.