Home

Description

fast-jwt provides fast JSON Web Token (JWT) implementation. Prior to 6.2.4, a critical authentication-bypass vulnerability in fast-jwt's async key-resolver flow allows any unauthenticated attacker to forge arbitrary JWTs that are accepted as authentic. When the application's key resolver returns an empty string (''), for example via the common keys[decoded.header.kid] || '' JWKS-style fallback, fast-jwt converts it to a zero-length Buffer, hands it to crypto.createSecretKey, derives allowedAlgorithms = ['HS256','HS384','HS512'] from it, and then verifies the token's signature against an empty-key HMAC. The attacker simply computes HMAC-SHA256(key='', input='${header}.${payload}'), which Node accepts without complaint — and the verifier returns the attacker-chosen payload (sub, admin, scopes, etc.) as authentic. This vulnerability is fixed in 6.2.4.

PUBLISHED Reserved 2026-05-05 | Published 2026-05-13 | Updated 2026-05-14 | Assigner GitHub_M




CRITICAL: 9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Problem types

CWE-287: Improper Authentication

CWE-326: Inadequate Encryption Strength

CWE-1391: Use of Weak Credentials

Product status

< 6.2.4
affected

References

github.com/...st-jwt/security/advisories/GHSA-gmvf-9v4p-v8jc exploit

github.com/...st-jwt/security/advisories/GHSA-gmvf-9v4p-v8jc

cve.org (CVE-2026-44351)

nvd.nist.gov (CVE-2026-44351)

Download JSON