CVE-2025-45768: pyjwt · Missing Encryption of Sensitive Data
Source CVE Database V5
Not known to be exploited · CVSS 7.0 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% 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
Users should review their use of pyjwt 2.10.1 to ensure that sufficiently strong keys are used, as the vendor indicates key length enforcement is the responsibility of the application. Monitor vendor advisories for any future updates or patches.
Description
pyjwt version 2.10.1 has a reported vulnerability involving weak encryption due to the lack of enforcement of a minimum key length. The supplier disputes the issue, stating that key length depends on the application using the library. The vulnerability has a high severity rating with a CVSS score of 7. No official patch or remediation guidance is currently available.