CVE-2025-45768 Weak cryptography in n/a
The pyjwt library allows weak encryption due to application-chosen key lengths, potentially enabling cryptographic bypasses.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-45768?
CVE-2025-45768 is a high-severity vulnerability in n/a, published on 31 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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).
Weakness: CWE-311
Which versions are affected by CVE-2025-45768?
1 open source package ship an affected version, including pyjwt. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
pyjwt PyPI | All versions to 2.10.1 | None |
Products include Pyjwt Project Pyjwt.
How do I fix CVE-2025-45768?
No fix published yet.
Is CVE-2025-45768 being exploited?
There is no known exploitation of CVE-2025-45768 in the wild and no public exploit code.
Other vulnerabilities in n/a
- CVE-2026-102268 PyJWT: Asymmetric-PEM detection bypass: whitespace/line-ending-mutated public keys skip the HS/asymmetric confusion guard
- CVE-2026-32597 PyJWT accepts unknown `crit` header extensions (RFC 7515 §4.1.11 MUST violation)
- CVE-2026-102266 PyJWK accepts empty HMAC keys, bypassing PyJWT's empty-key validation
- CVE-2026-102267 PyJWT: PyJWKClient follows redirects when fetching JWKS
- CVE-2026-102271 PyJWT: Public keys in DER form are accepted as HMAC secrets, bypassing the CVE-2022-29217 guard
Sources
Also known as CLSA-2025-1756858339, CLSA-2025-1757376737, DEBIAN-CVE-2025-45768, ECHO-3137-3dc7-eda3, GHSA-xpf8-484v-j9w6, MINI-57jg-w3p9-g2cw and 1 more.