Is github.com/siderolabs/omni 0.42 vulnerable?
Go · 4 releases from 0.42.0 to 0.42.3 · latest github.com/siderolabs/omni is 1.13.3 · checked 18 Nov 2026
Yes: 10 known advisories
Yes. github.com/siderolabs/omni 0.42.3, the last 0.42 release, is affected by 10 known security advisories (2 high, 1 medium, 7 low), including CVE-2026-45720, CVE-2025-61688, CVE-2025-59836. Upgrade to 1.6.6 or later to fix all of them.
go get github.com/siderolabs/omni@v1.6.6Is your project on an affected github.com/siderolabs/omni?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/siderolabs/omni 0.42.3
Omni: Operator can traverse image-factory API paths via unsanitized `talos_version` in CreateSchematic in github.com/siderolabs/omni
- Affected
- <1.6.6 · >=1.7.0 <1.7.3
- Fixed in
- 1.6.6, 1.7.3
Omni has a TOCTOU race condition that allows multiple concurrent uses of a single-use SAML session token in github.com/siderolabs/omni
- Affected
- <1.6.6 · >=1.7.0 <1.7.3
- Fixed in
- 1.6.6, 1.7.3
Omni: Operator can traverse image-factory API paths via unsanitized `talos_version` in CreateSchematic
- Affected
- <1.6.6 · >=1.7.0 <1.7.3
- Fixed in
- 1.6.6, 1.7.3
Omni has a TOCTOU race condition that allows multiple concurrent uses of a single-use SAML session token
- Affected
- <1.6.6 · >=1.7.0 <1.7.3
- Fixed in
- 1.6.6, 1.7.3
Omni is Vulnerable to DoS via Empty Create/Update Resource Requests in github.com/siderolabs/omni
- Affected
- <1.0.2 · >=1.1.0-beta.0 <1.1.5
- Fixed in
- 1.0.2, 1.1.5
Omni vulnerable to information leak via API in github.com/siderolabs/omni
- Affected
- <1.0.2 · >=1.1.0-beta.0 <1.1.5
- Fixed in
- 1.0.2, 1.1.5
Omni Wireguard SideroLink potential escape in github.com/siderolabs/omni
- Affected
- <0.48.0
- Fixed in
- 0.48.0
Omni vulnerable to information leak via API
- Affected
- >=1.1.0-beta.0 <1.1.5 · <1.0.2
- Fixed in
- 1.0.2, 1.1.5
Omni is Vulnerable to DoS via Empty Create/Update Resource Requests
- Affected
- >=1.1.0-beta.0 <1.1.5 · <1.0.2
- Fixed in
- 1.0.2, 1.1.5
Omni Wireguard SideroLink potential escape
- Affected
- <0.48.0
- Fixed in
- 0.48.0
Every github.com/siderolabs/omni 0.42.x release
Affected: 0.42.0 to 0.42.3. Latest github.com/siderolabs/omni: 1.13.3.
| Version | Known advisories |
|---|---|
| github.com/siderolabs/omni 0.42.3 | CVE-2026-45723, CVE-2026-45720, CVE-2026-45723, CVE-2026-45720, CVE-2025-59836, CVE-2025-61688, CVE-2025-59824, CVE-2025-61688, CVE-2025-59836, CVE-2025-59824 |
| github.com/siderolabs/omni 0.42.2 | CVE-2026-45723, CVE-2026-45720, CVE-2026-45723, CVE-2026-45720, CVE-2025-59836, CVE-2025-61688, CVE-2025-59824, CVE-2025-61688, CVE-2025-59836, CVE-2025-59824 |
| github.com/siderolabs/omni 0.42.1 | CVE-2026-45723, CVE-2026-45720, CVE-2026-45723, CVE-2026-45720, CVE-2025-59836, CVE-2025-61688, CVE-2025-59824, CVE-2025-61688, CVE-2025-59836, CVE-2025-59824 |
| github.com/siderolabs/omni 0.42.0 | CVE-2026-45723, CVE-2026-45720, CVE-2026-45723, CVE-2026-45720, CVE-2025-59836, CVE-2025-61688, CVE-2025-59824, CVE-2025-61688, CVE-2025-59836, CVE-2025-59824 |
Which of your client projects are still on github.com/siderolabs/omni 0.42?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/siderolabs/omni version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/siderolabs/omni versions
- github.com/siderolabs/omni 0.45
- github.com/siderolabs/omni 0.44
- github.com/siderolabs/omni 0.43
- github.com/siderolabs/omni 0.41
- github.com/siderolabs/omni 0.40
- github.com/siderolabs/omni 0.39
- github.com/siderolabs/omni 1.13
- github.com/siderolabs/omni 1.12
- github.com/siderolabs/omni 1.11
- github.com/siderolabs/omni 1.10
- github.com/siderolabs/omni 1.9
- github.com/siderolabs/omni 1.8
- All github.com/siderolabs/omni advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.