CVE-2026-45363 PUBLISHED

`jwt` (Ruby gem) - empty-key HMAC bypass

Assigner: GitHub_M
Reserved: 12.05.2026 Published: 14.07.2026 Updated: 15.07.2026

ruby-jwt is a Ruby implementation of the RFC 7519 OAuth JSON Web Token standard. Prior to 2.10.3 and 3.2.0, JWT.decode(token, '', true, algorithm: 'HS256') accepts an attacker-forged token because OpenSSL::HMAC.digest('SHA256', '', payload) returns a valid digest under an empty key and no empty-key precondition exists in the HMAC algorithm. The same path is reached when a keyfinder block or key_finder: argument returns an empty string, nil, or an array containing nil for an unknown key, affecting HS256, HS384, and HS512 verification through JWT.decode and JWT::EncodedToken#verify_signature!. This issue is fixed in versions 2.10.3 and 3.2.0.

Metrics

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

Product Status

Vendor jwt
Product ruby-jwt
Versions
  • Version < 2.10.3 is affected
  • Version >= 3.0.0, < 3.2.0 is affected

References

Problem Types

  • CWE-287: Improper Authentication CWE
  • CWE-326: Inadequate Encryption Strength CWE
  • CWE-1391: Use of Weak Credentials CWE