| Name | CVE-2026-45363 |
| Description | 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. |
| Source | CVE (at NVD; CERT, ENISA, LWN, oss-sec, fulldisc, Debian ELTS, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|---|---|---|
| ruby-jwt (PTS) | bullseye | 2.2.2-1 | vulnerable |
| bookworm | 2.5.0-1 | vulnerable | |
| trixie | 2.7.1-1 | vulnerable | |
| forky, sid | 3.2.0-1 | fixed |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|---|---|---|---|---|---|
| ruby-jwt | source | (unstable) | 3.2.0-1 |
https://github.com/jwt/ruby-jwt/security/advisories/GHSA-c32j-vqhx-rx3x
Fixed by: https://github.com/jwt/ruby-jwt/commit/db560b769a07bd9724e77ff505011ac01872106f (v3.2.0)
Fixed by: https://github.com/jwt/ruby-jwt/commit/9820020869ad147b941e49d96ab8beba35532964 (v2.10.3)