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

This month

HIGH 8.6REMOTEWATCHLISTUPGRADE

CVE-2025-61688 is a high-severity flaw (CVSS 8.6) 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, Omni might leak sensitive information via an API.

Why this priority

High severity
Remotely exploitable, no login, no user action
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	8.6 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.3% (top 76%)
CISA exploited list	No
Weakness	CWE-200
Published	2025-10-13
Last modified	2026-10-08

Publisher (CNA): GitHub, Inc. · Vendor: siderolabs

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

Am I affected?

Timeline

2025-10-13 21:15 UTCPublished CVE record published
2026-10-08 12:10 UTCUpdated Record last modified

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-61688?

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

Is CVE-2025-61688 being exploited?

CVE-2025-61688 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-61688 affect?

CVE-2025-61688 affects omni. Severity is high (CVSS 8.6). Omni manages Kubernetes on bare metal, virtual machines, or in a cloud. Prior to 1.1.5 and 1.0.2, Omni might leak sensitive information via an API.

How urgent is CVE-2025-61688?

Priority 46/100. High severity; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Kubernetes vulnerabilities

Related CVEs

CVE-2025-59836 MEDIUM 5.3 UPGRADE Omni manages Kubernetes on bare metal, virtual machines, or in a cloud
CVE-2025-59824 MEDIUM 5.4 UPGRADE Omni manages Kubernetes on bare metal, virtual machines, or in a cloud

References

← Back to latest CVEs