Is github.com/golang-jwt/jwt/v5 5.2 vulnerable?
Go · 4 releases from 5.2.0 to 5.2.3 · latest github.com/golang-jwt/jwt/v5 is 5.3.1 · checked 18 Nov 2026
No known advisories in the last release
github.com/golang-jwt/jwt/v5 5.2.3, the last 5.2 release, has no known advisories. 2 advisories affect earlier 5.2.x releases, so update to 5.2.3.
go get github.com/golang-jwt/jwt/v5@v5.2.3Is your project on an affected github.com/golang-jwt/jwt/v5?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 5.2.x, affecting earlier releases
Excessive memory allocation during header parsing in github.com/golang-jwt/jwt
- Affected
- >=5.0.0-rc.1 <5.2.2
- Fixed in
- 5.2.2
jwt-go allows excessive memory allocation during header parsing
- Affected
- >=5.0.0-rc.1 <5.2.2
- Fixed in
- 5.2.2
Every github.com/golang-jwt/jwt/v5 5.2.x release
Affected: 5.2.0 to 5.2.1. 5.2.2 and later are not affected. Latest github.com/golang-jwt/jwt/v5: 5.3.1.
| Version | Known advisories |
|---|---|
| github.com/golang-jwt/jwt/v5 5.2.3 | None |
| github.com/golang-jwt/jwt/v5 5.2.2 | None |
| github.com/golang-jwt/jwt/v5 5.2.1 | CVE-2025-30204, CVE-2025-30204 |
| github.com/golang-jwt/jwt/v5 5.2.0 | CVE-2025-30204, CVE-2025-30204 |
Which of your client projects are still on github.com/golang-jwt/jwt/v5 5.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/golang-jwt/jwt/v5 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/v5 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.