Is github.com/holiman/uint256 1.1 vulnerable?
Go · 2 releases from 1.1.0 to 1.1.1 · latest github.com/holiman/uint256 is 1.3.2 · checked 18 Nov 2026
No known advisories in the last release
github.com/holiman/uint256 1.1.1, the last 1.1 release, has no known advisories. 2 advisories affect earlier 1.1.x releases, so update to 1.1.1.
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
Fixed within 1.1.x, affecting earlier releases
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
Every github.com/holiman/uint256 1.1.x release
Affected: 1.1.0. 1.1.1 is not affected. Latest github.com/holiman/uint256: 1.3.2.
| Version | Known advisories |
|---|---|
| github.com/holiman/uint256 1.1.1 | None |
| github.com/holiman/uint256 1.1.0 | CVE-2020-26242, CVE-2020-26242 |
Which of your client projects are still on github.com/holiman/uint256 1.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.