jsonwebtoken vulnerabilities

JSON Web Token implementation (symmetric and asymmetric)

Registry
npm
Latest
9.0.3
License
MIT
Source
github.com/auth0/node-jsonwebtoken (opens the source repository in a new tab)

4 known advisories

The latest version, 9.0.3, is not affected by any of them. Projects on older versions may be.

Update to the latest version:npm install jsonwebtoken@9.0.3

Security advisories for jsonwebtoken

  • MediumGHSA-hjrf-2m68-595922 Dec 2022

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

    Affected
    <9.0.0
    Fixed in
    9.0.0
  • MediumGHSA-qwph-4952-7xr622 Dec 2022

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

    Affected
    <9.0.0
    Fixed in
    9.0.0
  • HighGHSA-8cf7-32gw-wr3322 Dec 2022

    jsonwebtoken unrestricted key type could lead to legacy keys usage

    Affected
    <9.0.0
    Fixed in
    9.0.0
  • CriticalGHSA-c7hr-j4mj-j2w69 Oct 2018

    Verification Bypass in jsonwebtoken

    Affected
    <4.2.2
    Fixed in
    4.2.2

Which of your client projects still run an old jsonwebtoken?

NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml 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.

Scan a project free, no signupOr connect GitHub to scan every repo

Other npm packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.