Skip to content
Fencer Vulns
medium 6.4

CVE-2022-23540 json

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

published 2022-12-22 3 y ago modified 2026-06-17 4 mo ago also GHSA-qwph-4952-7xr6 , EUVD-2022-7728

cvss
6.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 47%
public exploits
0
none known

Summary

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 don’t need to allow for the `none` algorithm. If you need 'none' algorithm, you have to explicitly specify that in `jwt.verify()` options.

Patch / fix

  • npm jsonwebtoken 9.0.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-23540 updated cvss 6.4

jsonwebtoken: Insecure default algorithm in jwt.verify() could lead to signature validation bypass

  • Red Hat OpenShift Container Platform 4 openshift4/ose-console
    affected: no fix available
  • Red Hat Openshift Container Storage 4 ocs4/mcg-core-rhel8
    affected: no fix planned “Out of support scope”
  • Red Hat RHODF 4.13 for RHEL 9 odf4/mcg-core-rhel9 v4.13.0-41
    fixed: vendor fix RHSA-2023:3742
  • Red Hat RHODF 4.13 for RHEL 9 odf4/cephcsi-rhel9 v4.13.0-35, odf4/mcg-cli-rhel9 v4.13.0-17, odf4/odf-console-rhel9 v4.13.0-85, odf4/mcg-rhel9-operator v4.13.0-41, odf4/ocs-rhel9-operator v4.13.0-67, odf4/odf-rhel9-operator v4.13.0-24, +17 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.57% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.4 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:L
NVD 3.1 7.6 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L
GitHub 3.1 6.4 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:L

Affected packages

ecosystem package affected fixed in
npm jsonwebtoken
<9.0.0
9.0.0

Affected products

  • auth0 node-jsonwebtoken

Classification

Weakness
  • CWE-287 Improper Authentication
  • CWE-347 Improper Verification of Cryptographic Signature
  • CWE-327 Use of a Broken or Risky Cryptographic Algorithm

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.