CVE-2025-45770: jwt · Inadequate Encryption Strength
Source CVE Database V5
Not known to be exploited · CVSS 7.0 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:HExploitation evidence
Disclosed: evidence found.
CVE published 31 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
European organizations should immediately audit their use of the jwt library to determine if version 5.4.3 or similar vulnerable versions are in use. They should verify that cryptographic keys used for JWT signing and encryption meet strong security standards, including adequate key lengths and secure key generation practices. Since the vulnerability is related to weak encryption rather than a direct code flaw, enforcing strict cryptographic policies is critical. Organizations should consider upgrading to newer versions of the jwt library if available, or applying patches once released. Additionally, implementing defense-in-depth measures such as token expiration, token revocation mechanisms, and monitoring for anomalous authentication activity can reduce risk. Security teams should also educate developers on proper key management and cryptographic best practices to prevent misuse. Finally, regular penetration testing and code reviews focusing on JWT handling can help identify and remediate weaknesses before exploitation.
Description
jwt v5.4.3 was discovered to contain weak encryption. NOTE: this issue has been disputed on the basis that key lengths are expected to be set by an application, not by this library. This dispute is subject to review under CNA rules 4.1.4, 4.1.14, and other rules; the dispute tagging is not meant to recommend an outcome for this CVE Record.