CVE-2026-45363
CRITICALDescription
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.
How to fix
This vulnerability affects an unusually large number of packages. The highest-confidence fixes are shown above; the full list is longer. Check the referenced advisories for complete coverage.
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 15% of all known CVEs.
References
Related Vulnerabilities
Other CWE-287 (Improper Authentication) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2023-35082 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2023-35078 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2017-7921 | Critical | 9.8 | 100% | KEV | - |
| CVE-2024-7593 | Critical | 9.8 | 100% | KEV | - |
| CVE-2023-46805 | High | 8.2 | 100% | KEV + Ransom | - |
| CVE-2022-40684 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
Common questions
How do I fix CVE-2026-45363?
Published advisories record a fix for 117 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2026-45363 being actively exploited?
Not that we know of. CVE-2026-45363 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.24% is the estimated probability that it will be exploited in the next 30 days. That is higher than 15% of all scored CVEs.
How severe is CVE-2026-45363?
CVE-2026-45363 has a CVSS v3 base score of 9.1, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-45363 affect?
Published advisories record a fix for ruby-jwt (Debian), ansible-core (Rocky), ansible-core (Red Hat / RHEL), ansible-test (Red Hat / RHEL), and 113 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-45363
Markdown
[](https://tridentstack.com/cve/CVE-2026-45363)HTML
<a href="https://tridentstack.com/cve/CVE-2026-45363"><img src="https://tridentstack.com/cve/badge/CVE-2026-45363.svg" alt="CVE-2026-45363"></a>Check your Linux endpoints for this class of vulnerability
TridentStack Control continuously scans Linux endpoints for known vulnerabilities and deploys the fixes from the same console. 200 endpoints free forever, no credit card.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-07-15.