Auth0 Jsonwebtoken
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Auth0 Jsonwebtoken.
By the Year
In 2026 there have been 0 vulnerabilities in Auth0 Jsonwebtoken. Jsonwebtoken did not have any published security vulnerabilities last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 0 | 0.00 |
| 2025 | 0 | 0.00 |
| 2024 | 0 | 0.00 |
| 2023 | 0 | 0.00 |
| 2022 | 3 | 7.33 |
It may take a day or so for new Jsonwebtoken vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Auth0 Jsonwebtoken Security Vulnerabilities
jsonwebtoken 8.5.1 insecure key type misuse upgrade to 9.0.0
CVE-2022-23539
8.1 - High
- December 23, 2022
Versions `<=8.5.1` of `jsonwebtoken` library could be misconfigured so that legacy, insecure key types are used for signature verification. For example, DSA keys could be used with the RS256 algorithm. You are affected if you are using an algorithm and a key type other than a combination listed in the GitHub Security Advisory as unaffected. This issue has been fixed, please update to version 9.0.0. This version validates for asymmetric key type and algorithm combinations. Please refer to the above mentioned algorithm / key type combinations for the valid secure configuration. After updating to version 9.0.0, if you still intend to continue with signing or verifying tokens using invalid key type/algorithm value combinations, youll need to set the `allowInvalidAsymmetricKeyTypes` option to `true` in the `sign()` and/or `verify()` functions.
Use of a Broken or Risky Cryptographic Algorithm
jsonwebtoken <=8.5.1: none-algorithm bypass in jwt.verify() (fixed 9.0.0)
CVE-2022-23540
7.6 - High
- December 22, 2022
In versions `<=8.5.1` of `jsonwebtoken` library, lack of algorithm definition in the `jwt.verify()` function can lead to signature validation bypass due to defaulting to the `none` algorithm for signature verification. Users are affected if you do not specify algorithms in the `jwt.verify()` function. This issue has been fixed, please update to version 9.0.0 which removes the default support for the none algorithm in the `jwt.verify()` method. There will be no impact, if you update to version 9.0.0 and you dont need to allow for the `none` algorithm. If you need 'none' algorithm, you have to explicitly specify that in `jwt.verify()` options.
Improper Verification of Cryptographic Signature
jsonwebtoken <=8.5.1 JWT Verification Bypass (Sym/Asym Mix)
CVE-2022-23541
6.3 - Medium
- December 22, 2022
jsonwebtoken is an implementation of JSON Web Tokens. Versions `<= 8.5.1` of `jsonwebtoken` library can be misconfigured so that passing a poorly implemented key retrieval function referring to the `secretOrPublicKey` argument from the readme link will result in incorrect verification of tokens. There is a possibility of using a different algorithm and key combination in verification, other than the one that was used to sign the tokens. Specifically, tokens signed with an asymmetric public key could be verified with a symmetric HS256 algorithm. This can lead to successful validation of forged tokens. If your application is supporting usage of both symmetric key and asymmetric key in jwt.verify() implementation with the same key retrieval function. This issue has been patched, please update to version 9.0.0.
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Auth0 Jsonwebtoken or by Auth0? Click the Watch button to subscribe.
