LowGO-2022-0244CVE-2021-3538GHSA-33m6-q9v5-62r7
Insufficient randomness in UUIDs in github.com/satori/go.uuid
Published 15 Jul 2022 · Updated 13 Mar 2026
Is your project on an affected github.com/satori/go.uuid?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=1.2.1-0.20180103161547-0ef6afb2f6cd <1.2.1-0.20180404165556-75cca531ea76
- Fixed in
- 1.2.1-0.20180404165556-75cca531ea76
Update to the fixed version for your release line, for example:
go get github.com/satori/go.uuid@v1.2.1-0.20180404165556-75cca531ea76Details
Random data used to create UUIDs can contain zeros, resulting in predictable UUIDs and possible collisions.
Is GO-2022-0244 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/satori/go.uuid, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.