https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 04:26:26 +0000 https://vulnerability.circl.lu/vuln/cve-2026-45363 <p><strong>Affected:</strong> jwt ruby-jwt</p> <p>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, &#39;&#39;, true, algorithm: &#39;HS256&#39;) accepts an attacker-forged token because OpenSSL::HMAC.digest(&#39;SHA256&#39;, &#39;&#39;, 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.</p> <p><strong>Affected:</strong> jwt ruby-jwt</p> <p>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, &#39;&#39;, true, algorithm: &#39;HS256&#39;) accepts an attacker-forged token because OpenSSL::HMAC.digest(&#39;SHA256&#39;, &#39;&#39;, 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.</p> https://vulnerability.circl.lu/vuln/cve-2026-45363