LowGO-2024-3250CVE-2024-51744GHSA-29wx-vh33-7x7r

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

Published 12 Nov 2024 · Updated 4 Feb 2026

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

Affected package

Affected
<4.5.1
Fixed in
4.5.1
Update to the fixed version for your release line, for example:go get github.com/golang-jwt/jwt/v4@v4.5.1

Details

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

Is GO-2024-3250 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/golang-jwt/jwt/v4, and gives you the command that fixes it.

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

  • LowCVE-2025-30204Excessive memory allocation during header parsing in github.com/golang-jwt/jwt · 26 Mar 2025
  • HighCVE-2025-30204jwt-go allows excessive memory allocation during header parsing · 21 Mar 2025
github.com/golang-jwt/jwt/v4 security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.