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

Go · 1 release from 2.6.0 to 2.6.0 · latest gopkg.in/square/go-jose.v2 is 2.6.0 · checked 20 Nov 2026

Yes: 2 known advisories

Yes. gopkg.in/square/go-jose.v2 2.6.0, the last 2.6 release, is affected by 2 known security advisories (1 medium, 1 low), including CVE-2024-28180, CVE-2024-28180. At least one has no fixed release yet.

Is your project on an affected gopkg.in/square/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

Advisories affecting gopkg.in/square/go-jose.v2 2.6.0

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

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

    Affected
    All versions
    Fixed in
    No fix released
  • MediumCVE-2024-28180GHSA-c5q2-7r4c-mv6g7 Mar 2024

    Go JOSE vulnerable to Improper Handling of Highly Compressed Data (Data Amplification)

    Affected
    <=2.6.0
    Fixed in
    No fix released

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

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact gopkg.in/square/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/square/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.