CVE-2026-45363

ruby-jwt: ruby-jwt is a Ruby implementation of the RFC 7519 OAuth JSON Web Token standard

CVE-2026-45363 is fixed in ruby-jwt on 1 platform, first by DEBIAN-CVE-2026-45363, released July 19, 2026. It is not reported as exploited. Patch Radar priority: Urgent.

Urgent
CVSS
9.1
critical
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0036
30th percentile

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.

Where it's fixed

ProductFixed inFixReleased
Linux
ruby-jwt · Debian 12.15 (bookworm) 2.5.0-1+deb12u1 DEBIAN-CVE-2026-45363 Jul 19, 2026
ruby-jwt · Debian 13.5 (trixie) 2.7.1-1+deb13u1 DEBIAN-CVE-2026-45363 Jul 19, 2026
ruby-jwt · Debian 14 3.2.0-1 DEBIAN-CVE-2026-45363 Jul 19, 2026

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.