LowGO-2025-3553CVE-2025-30204GHSA-mh63-6h87-95cp
Excessive memory allocation during header parsing in github.com/golang-jwt/jwt
Published 26 Mar 2025 · Updated 14 Nov 2026
Is your project on an affected github.com/golang-jwt/jwt?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- All versions
- Fixed in
- No fix released
- Affected
- <4.5.2
- Fixed in
- 4.5.2
Update to the fixed version for your release line, for example:
go get github.com/golang-jwt/jwt/v4@v4.5.2- Affected
- >=5.0.0-rc.1 <5.2.2
- Fixed in
- 5.2.2
Update to the fixed version for your release line, for example:
go get github.com/golang-jwt/jwt/v5@v5.2.2Details
Excessive memory allocation during header parsing in github.com/golang-jwt/jwt
Is GO-2025-3553 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, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.