Jwt vulnerabilities
2 vulnerabilities
Known vulnerabilities in Jwt products, newest first, with CVSS severity, EPSS, KEV listings and ransomware use, across 2 products.
Products
2PrioritiseCVE-2026-45363jwt · ruby-jwt +36 more`jwt` (Ruby gem) - empty-key HMAC bypassruby-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.CVSS9.1CriticalEPSS0.36%PrioritiseCVE-2025-54887jwt · ruby-jwe +1 morejwe: Missing AES-GCM authentication tag validation in encrypted JWEsjwe is a Ruby implementation of the RFC 7516 JSON Web Encryption (JWE) standard. In versions 1.1.0 and below, authentication tags of encrypted JWEs can be brute forced, which may result in loss of confidentiality for those JWEs and provide ways to craft arbitrary JWEs. This puts users at risk because JWEs can be modified to decrypt to an arbitrary value, decrypted by observing parsing differences and the GCM internal GHASH key can be recovered. Users are affected by this vulnerability even if they do not use an AES-GCM encryption algorithm for their JWEs. As the GHASH key may have been leaked, users must rotate the encryption keys after upgrading. This issue is fixed in version 1.1.1.CVSS9.1CriticalEPSS0.27%