New MCP server — Bring vulnerability intelligence into your AI
Back to feed

CVE-2026-45363

NVDCIRCLENISA

EUVD-2026-44516 · Published Jul 14, 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.

Technologies

Jwt Jwt

Weaknesses

CWE-326CWE-287CWE-1391

CVSS scores

  • v3.19.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

MITRE ATT&CK

Inferred

Where this vulnerability fits in an attack

Initial Access Credential Access

References

Potentially impacted assets

See if this affects your attack surface

Take 15 minutes to discover our platform with our experts

PatrowlIntel platform screenshot