CVE-2026-107724CWE-347

CVE-2026-107724

High · published October 9, 2026

CVSS v3.1
7.4
EPSS
0%
Percentile
12.1
In the wild
Unconfirmed
What it is

fast-jwt provides fast JSON Web Token (JWT) implementation. In 6.2.4, fast-jwt can classify raw serialized public JWK or JWKS JSON as an HMAC secret because src/crypto.js performDetectPublicKeyAlgorithms treats non-PEM strings as symmetric key material. If HS256 is explicitly allowed or inferred, an attacker who knows the exact serialized public-key bytes can use those bytes as an HMAC key and create a token containing arbitrary claims that createVerifier accepts. Serialization ordering or whitespace differences can prevent exploitation, and applications using supported PEM keys with an asymmetric-only algorithm allowlist are not affected. This issue is fixed in version 6.3.0.

The record
Technical detail
CVSS v3.1
7.4 · HIGH
Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
CVSS v4.0
Not supplied
EPSS
0.00222 · 12.1th percentile
Weakness
CWE-347 · Improper Verification of Cryptographic Signature
Published
2026-10-09T02:17Z
References (5)
EPSS history
Timeline
  • 10 OCT 03:27Z
    EPSS moved — → 0%
    epss
  • 08 OCT 21:53Z
    fast-jwt treats raw public JWK JSON as an HMAC secret, enabling HS256 token forgery
    cvelistv5
  • 08 OCT 21:53Z
    fast-jwt treats raw public JWK JSON as an HMAC secret, enabling HS256 token forgery
    cvelistv5