github.com/golang-jwt/jwt/v4 vulnerabilities

Registry
Go
Latest
4.5.2

4 known advisories

The latest version, 4.5.2, is not affected by any of them. Projects on older versions may be.

Update to the latest version: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

Security advisories for github.com/golang-jwt/jwt/v4

  • 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

Is your github.com/golang-jwt/jwt/v4 version vulnerable?

Which of your client projects still run an old github.com/golang-jwt/jwt/v4?

NPMscan reads the go.mod in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other Go packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Go registry.