Is github.com/golang-jwt/jwt/v4 4.1 vulnerable?

Go · 1 release from 4.1.0 to 4.1.0 · latest github.com/golang-jwt/jwt/v4 is 4.5.2 · checked 18 Nov 2026

Yes: 4 known advisories

Yes. github.com/golang-jwt/jwt/v4 4.1.0, the last 4.1 release, is affected by 4 known security advisories (1 high, 3 low), including CVE-2025-30204, CVE-2025-30204, CVE-2024-51744. Upgrade to 4.5.2 or later to fix all of them.

Upgrade with:go get github.com/golang-jwt/jwt/v4@v4.5.2

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

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/v4 4.1.0

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

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

    Affected
    <4.5.2
    Fixed in
    4.5.2
  • HighCVE-2025-30204GHSA-mh63-6h87-95cp21 Mar 2025

    jwt-go allows excessive memory allocation during header parsing

    Affected
    <4.5.2
    Fixed in
    4.5.2
  • LowCVE-2024-51744GO-2024-325012 Nov 2024

    Improper error handling in ParseWithClaims and bad documentation may cause dangerous situations in github.com/golang-jwt/jwt

    Affected
    <4.5.1
    Fixed in
    4.5.1
  • LowCVE-2024-51744GHSA-29wx-vh33-7x7r4 Nov 2024

    Bad documentation of error handling in ParseWithClaims can lead to potentially dangerous situations

    Affected
    <4.5.1
    Fixed in
    4.5.1

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

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/golang-jwt/jwt/v4 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/v4 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.