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.
go get github.com/golang-jwt/jwt/v4@v4.5.2Is your project on an affected github.com/golang-jwt/jwt/v4?
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
Excessive memory allocation during header parsing in github.com/golang-jwt/jwt
- Affected
- <4.5.2
- Fixed in
- 4.5.2
jwt-go allows excessive memory allocation during header parsing
- Affected
- <4.5.2
- Fixed in
- 4.5.2
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
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?
- github.com/golang-jwt/jwt/v4 4.5No known advisories in 4.5.2
- github.com/golang-jwt/jwt/v4 4.44 advisories in 4.4.3
- github.com/golang-jwt/jwt/v4 4.34 advisories in 4.3.0
- github.com/golang-jwt/jwt/v4 4.24 advisories in 4.2.0
- github.com/golang-jwt/jwt/v4 4.14 advisories in 4.1.0
- github.com/golang-jwt/jwt/v4 4.04 advisories in 4.0.0
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.