github.com/golang-jwt/jwt vulnerabilities
- Registry
- Go
- Latest
- 3.2.2+incompatible
2 known advisories
The latest version, 3.2.2+incompatible, is affected by 2 of them.
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
Security advisories for github.com/golang-jwt/jwt
Excessive memory allocation during header parsing in github.com/golang-jwt/jwt
- Affected
- All versions
- Fixed in
- No fix released
jwt-go allows excessive memory allocation during header parsing
- Affected
- >=3.2.0 <=3.2.2
- Fixed in
- No fix released
Is your github.com/golang-jwt/jwt version vulnerable?
- github.com/golang-jwt/jwt 3.22 advisories in 3.2.2
- github.com/golang-jwt/jwt 3.11 advisory in 3.1.0
- github.com/golang-jwt/jwt 3.01 advisory in 3.0.0
- github.com/golang-jwt/jwt 2.71 advisory in 2.7.0
- github.com/golang-jwt/jwt 2.61 advisory in 2.6.0
- github.com/golang-jwt/jwt 2.51 advisory in 2.5.0
- github.com/golang-jwt/jwt 2.41 advisory in 2.4.0
- github.com/golang-jwt/jwt 2.31 advisory in 2.3.0
- github.com/golang-jwt/jwt 2.21 advisory in 2.2.0
- github.com/golang-jwt/jwt 1.01 advisory in 1.0.2
Which of your client projects still run an old github.com/golang-jwt/jwt?
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
- github.com/containerd/containerd
- github.com/xuri/excelize/v2
- github.com/microcosm-cc/bluemonday
- go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp
- github.com/jackc/pgx
- github.com/caddyserver/caddy/v2
- github.com/goadesign/goa
- go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Go registry.