CVE-2025-45768
High CVSS 7.0
- OSV id
- PYSEC-2025-183
- Also known as
- CVE-2025-45768
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| pyjwt PyPI |
<= 2.10.1 | after 2.10.1 |
Versions we track that it affects: pyjwt 2.8.0
How to fix it
No fix yet. No fixed version of pyjwt has been released yet.
- Check the advisory and its references below for a workaround or a configuration change that turns off the affected feature.
- Limit exposure: don't pass untrusted input to the affected code path, and keep it off public endpoints if you can.
- Pin away from the affected versions if an older release is not affected, or consider replacing the package.
- Watch for the fix: a free AIssue account checks your lockfiles every day and emails you when a fixed version is released.
Not sure whether your project uses an affected version? Check your lockfile below for free.
Details
pyjwt v2.10.1 was discovered to contain weak encryption. NOTE: this is disputed by the Supplier because the key length is chosen by the application that uses the library (admittedly, library users may benefit from a minimum value and a mechanism for opting in to strict enforcement).
References
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: Python Packaging Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.