Is gopkg.in/go-jose/go-jose.v2 2.2 vulnerable?
Go · 3 releases from 2.2.0 to 2.2.2 · latest gopkg.in/go-jose/go-jose.v2 is 2.6.3 · checked 20 Nov 2026
Yes: 2 known advisories
Yes. gopkg.in/go-jose/go-jose.v2 2.2.2, the last 2.2 release, is affected by 2 known security advisories (1 medium, 1 low), including CVE-2024-28180, CVE-2024-28180. Upgrade to 2.6.3 or later to fix all of them.
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
Advisories affecting gopkg.in/go-jose/go-jose.v2 2.2.2
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
Every gopkg.in/go-jose/go-jose.v2 2.2.x release
Affected: 2.2.0 to 2.2.2. Latest gopkg.in/go-jose/go-jose.v2: 2.6.3.
| Version | Known advisories |
|---|---|
| gopkg.in/go-jose/go-jose.v2 2.2.2 | CVE-2024-28180, CVE-2024-28180 |
| gopkg.in/go-jose/go-jose.v2 2.2.1 | CVE-2024-28180, CVE-2024-28180 |
| gopkg.in/go-jose/go-jose.v2 2.2.0 | CVE-2024-28180, CVE-2024-28180 |
Which of your client projects are still on gopkg.in/go-jose/go-jose.v2 2.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact gopkg.in/go-jose/go-jose.v2 version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other gopkg.in/go-jose/go-jose.v2 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.