Is gopkg.in/go-jose/go-jose.v2 2.6 vulnerable?

Go · 4 releases from 2.6.0 to 2.6.3 · latest gopkg.in/go-jose/go-jose.v2 is 2.6.3 · checked 20 Nov 2026

No known advisories in the last release

gopkg.in/go-jose/go-jose.v2 2.6.3, the last 2.6 release, has no known advisories. 2 advisories affect earlier 2.6.x releases, so update to 2.6.3.

Update within 2.6:go get gopkg.in/go-jose/go-jose.v2@v2.6.3

Is your project on an affected gopkg.in/go-jose/go-jose.v2?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 2.6.x, affecting earlier releases

  • LowCVE-2024-28180GO-2024-263115 Mar 2024

    Decompression bomb vulnerability in github.com/go-jose/go-jose

    Affected
    <2.6.3
    Fixed in
    2.6.3
  • MediumCVE-2024-28180GHSA-c5q2-7r4c-mv6g7 Mar 2024

    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.6.x release

Affected: 2.6.0 to 2.6.2. 2.6.3 is not affected.

VersionKnown advisories
gopkg.in/go-jose/go-jose.v2 2.6.3None
gopkg.in/go-jose/go-jose.v2 2.6.2CVE-2024-28180, CVE-2024-28180
gopkg.in/go-jose/go-jose.v2 2.6.1CVE-2024-28180, CVE-2024-28180
gopkg.in/go-jose/go-jose.v2 2.6.0CVE-2024-28180, CVE-2024-28180

Which of your client projects are still on gopkg.in/go-jose/go-jose.v2 2.6?

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.