Auth0 jsonwebtoken

In jsonwebtoken node module before 4.2.2 it is possible for an attacker to bypass verification when a token digitally signed with an asymmetric key (RS/ES family) of algorithms but instead the attacker send a token digitally signed with a symmetric algorithm (HS* family).

jsonwebtoken unrestricted key type could lead to legacy keys usage

jsonwebtoken vulnerable to signature validation bypass due to insecure default algorithm in jwt.verify()

jsonwebtoken's insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC