Skip to main content
VulnerabilityPublished Updated

CVE-2025-61688: github.com/siderolabs/omni · Omni vulnerable to information leak via API

Affects github.com/siderolabs/omniSource GCVE Database

0
Compare
Authoritative record:CVE-2025-61688· High 8.6

Not known to be exploited · CVSS 8.6 High : upgrade to 1.1.5 soon.

Data as of 4 Nov 2026, 17:16 UTC

CVSS 3.1 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.1.5, 1.0.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

What to do

Upgrade github.com/siderolabs/omni to 1.1.5; github.com/siderolabs/omni to 1.0.2.

Affected software

ProductAffectedFixed in
Gogithub.com/siderolabs/omniAffected
  • >=1.1.0-beta.0 <1.1.5
Fixed in
  • 1.1.5
Gogithub.com/siderolabs/omniAffected
  • <1.0.2
Fixed in
  • 1.0.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

### Impact Omni might leak sensitive information via an API. ### Patches v1.1.5, v1.0.2 and v1.2.0 contain the patch. ### Workarounds None. ### References None.

References

Community reviews

Loading reviews…