p PatchFirst

CVE-2026-44351

CVE-2026-44351 · fast-jwt: Empty HMAC secret accepted via async key resolver - JWT auth bypass

Cette page présente des faits issus de sources publiques. Consultez l’avis original avant toute mise à jour.

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.

CVSS 9.1 · Critique · EPSS 0,2% · Correctif disponible

Publication
Mise à jour

Pile logicielle: node

Produits et versions concernés

  • fast-jwt

    Versions du logiciel
    • < 6.2.4: Concernée

    Aucun correctif publié

  • fast-jwt npm

    Plages de versions concernées
    • SEMVER: < 6.2.4

    Mettez à jour vers 6.2.4

Sources originales

Vérifiez votre serveur →