CVE-2022-23539

What it is

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, you’ll need to set the `allowInvalidAsymmetricKeyTypes` option to `true` in the `sign()` and/or `verify()` functions.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. High risk of data tampering.

Exploit odds

0.5% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2022-12-23 00:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 04:30 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.5% in the next 30 days (EPSS).
• Severity: 5.9 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2022-12-23 00:15 UTC

Last modified

2026-06-17 04:30 UTC

Exploit probability

0.5% · EPSS, next 30 days

Weakness

CWE-327 · Broken cryptographic algorithm

Record status

Modified

Affected

• auth0 Jsonwebtoken ≤ 8.5.1

Attack profile CVSS 3.1 · 5.9

Attack vector

Network

Complexity

High

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2022-23539.md and follow it. Check whether this project is affected by CVE-2022-23539. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge