Is github.com/holiman/uint256 0.1 vulnerable?
Go · 1 release from 0.1.0 to 0.1.0 · latest github.com/holiman/uint256 is 1.3.2 · checked 18 Nov 2026
Yes: 2 known advisories
Yes. github.com/holiman/uint256 0.1.0, the last 0.1 release, is affected by 2 known security advisories (1 medium, 1 low), including CVE-2020-26242, CVE-2020-26242. Upgrade to 1.1.1 or later to fix all of them.
go get github.com/holiman/uint256@v1.1.1Is your project on an affected github.com/holiman/uint256?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/holiman/uint256 0.1.0
Denial of service in github.com/holiman/uint256
- Affected
- >=0.1.0 <1.1.1
- Fixed in
- 1.1.1
Denial of service in geth
- Affected
- >=0.1.0 <1.1.1
- Fixed in
- 1.1.1
Which of your client projects are still on github.com/holiman/uint256 0.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/holiman/uint256 version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/holiman/uint256 versions
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.