CVE-2025-61688: Omni vulnerable to information leak via API
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.
Published Oct 13, 2025 · Updated Nov 5, 2025
Affected packages
github.com/siderolabs/omni
- Ecosystem
- Go
- Affected
- >= 1.1.0-beta.0, <= 1.1.4
- Fixed in
- 1.1.5
- Check
go list -m github.com/siderolabs/omni
github.com/siderolabs/omni
- Ecosystem
- Go
- Affected
- <= 1.0.1
- Fixed in
- 1.0.2
- Check
go list -m github.com/siderolabs/omni
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
Credited to utkuozdemir.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-45720
Omni has a TOCTOU race condition that allows multiple concurrent uses of a single-use SAML session token
high7.0Jun 5, 2026CVE-2026-45723
Omni: Operator can traverse image-factory API paths via unsanitized `talos_version` in CreateSchematic
low2.7Jun 5, 2026CVE-2026-45726
Omni: Reader-level users can retrieve imported cluster CA keys via ResourceService
high7.6Jun 5, 2026CVE-2025-59836
Omni is Vulnerable to DoS via Empty Create/Update Resource Requests
medium5.3Oct 13, 2025CVE-2025-59824
Omni Wireguard SideroLink potential escape
low0.5Sep 24, 2025
