gopkg.in/go-jose/go-jose.v2 vulnerabilities
- Registry
- Go
- Latest
- 2.6.3
2 known advisories
The latest version, 2.6.3, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
go get gopkg.in/go-jose/go-jose.v2@v2.6.3Is your project on an affected gopkg.in/go-jose/go-jose.v2?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for gopkg.in/go-jose/go-jose.v2
Decompression bomb vulnerability in github.com/go-jose/go-jose
- Affected
- <2.6.3
- Fixed in
- 2.6.3
Go JOSE vulnerable to Improper Handling of Highly Compressed Data (Data Amplification)
- Affected
- <2.6.3
- Fixed in
- 2.6.3
Is your gopkg.in/go-jose/go-jose.v2 version vulnerable?
- gopkg.in/go-jose/go-jose.v2 2.6No known advisories in 2.6.3
- gopkg.in/go-jose/go-jose.v2 2.52 advisories in 2.5.1
- gopkg.in/go-jose/go-jose.v2 2.42 advisories in 2.4.1
- gopkg.in/go-jose/go-jose.v2 2.32 advisories in 2.3.1
- gopkg.in/go-jose/go-jose.v2 2.22 advisories in 2.2.2
- gopkg.in/go-jose/go-jose.v2 2.12 advisories in 2.1.9
Which of your client projects still run an old gopkg.in/go-jose/go-jose.v2?
NPMscan reads the go.mod in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Go packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Go registry.