CVE-2026-107724

published 8 Oct 2026 · updated 9 Oct 2026

fast-jwt treats raw public JWK JSON as an HMAC secret, enabling HS256 token forgery

7.4HighCVSS 7.4EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
nearform>=6.2.4 <6.3.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-107724 severity on Zeptric[![CVE-2026-107724](https://zeptric.io/badge/cve/CVE-2026-107724.svg)](https://zeptric.io/cve/CVE-2026-107724)