CVE-2025-45768: 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).

CSIRTS triage

What: The library uses weak encryption when configured with short key lengths, though key length selection is delegated to the application.
Who is affected: Applications using PyJWT 2.10.1 with insufficient key lengths are affected.
Urgency: Moderate; not exploited and disputed by supplier as application-level configuration issue, but users may benefit from stronger defaults.
Action: Review key length configuration in applications using PyJWT and consider upgrading to a version with enforced minimum key length or explicit warnings.

AI-assisted analysis generated from the source advisory — verify against the original.

⚡ Watch PyJWT

Get an email when a new PyJWT advisory drops — max one per day, one-click unsubscribe.

EPSS (FIRST.org) estimates each CVE’s probability of exploitation in the next 30 days — here is the CSIRTS.com read on those numbers.

Low exploitation riskCVE-2025-457680.16% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 5% of all EPSS-scored CVEs.

CVE	CSIRTS overview	External
CVE-2025-45768	coverage & exploitation status	NVD · CVE.org