Is github.com/golang-jwt/jwt 3.2 vulnerable?

Go · 3 releases from 3.2.0 to 3.2.2 · latest github.com/golang-jwt/jwt is 3.2.2+incompatible · checked 18 Nov 2026

Yes: 2 known advisories

Yes. github.com/golang-jwt/jwt 3.2.2, the last 3.2 release, is affected by 2 known security advisories (1 high, 1 low), including CVE-2025-30204, CVE-2025-30204. At least one has no fixed release yet.

Is your project on an affected github.com/golang-jwt/jwt?

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 github.com/golang-jwt/jwt 3.2.2

  • LowCVE-2025-30204GO-2025-355326 Mar 2025

    Excessive memory allocation during header parsing in github.com/golang-jwt/jwt

    Affected
    All versions
    Fixed in
    No fix released
  • HighCVE-2025-30204GHSA-mh63-6h87-95cp21 Mar 2025

    jwt-go allows excessive memory allocation during header parsing

    Affected
    >=3.2.0 <=3.2.2
    Fixed in
    No fix released

Every github.com/golang-jwt/jwt 3.2.x release

Affected: 3.2.0 to 3.2.2. Latest github.com/golang-jwt/jwt: 3.2.2+incompatible.

VersionKnown advisories
github.com/golang-jwt/jwt 3.2.2CVE-2025-30204, CVE-2025-30204
github.com/golang-jwt/jwt 3.2.1CVE-2025-30204, CVE-2025-30204
github.com/golang-jwt/jwt 3.2.0CVE-2025-30204, CVE-2025-30204

Which of your client projects are still on github.com/golang-jwt/jwt 3.2?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/golang-jwt/jwt version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other github.com/golang-jwt/jwt 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.