CVE-2026-107724 PUBLISHED

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

Assigner: GitHub_M
Reserved: 08.10.2026 Published: 08.10.2026 Updated: 09.10.2026

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.

Metrics

CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
CVSS Score: 7.4

Product Status

Vendor nearform
Product fast-jwt
Versions
  • Version >= 6.2.4, < 6.3.0 is affected

References

Problem Types

  • CWE-347: Improper Verification of Cryptographic Signature CWE