LowPYSEC-2025-183CVE-2025-45768
PYSEC-2025-183 in pyjwt
Published 31 Jul 2025 · Updated 21 May 2026
Is your project on an affected pyjwt?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
pyjwtPyPI
- Affected
- <=2.10.1
- Fixed in
- No fix released
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).
Is PYSEC-2025-183 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected pyjwt, and gives you the command that fixes it.
More advisories for pyjwt
- HighGHSA-pxh4-856f-4h89PyJWT: HS256/384/512 verify accepts empty HMAC key via oct JWK (PyJWK/PyJWKClient) enabling token forgery · 22 Oct 2026
- MediumCVE-2026-102275PyJWT accepts inconsistent OKP x/d JWKs, causing public/private key identity confusion · 5 Oct 2026
- MediumCVE-2026-103001PyJWT.decode() reintroduces options-dict mutation, enabling silent claim-verification bypass on dict reuse · 30 Sept 2026
- MediumCVE-2026-101918PyJWT: Unauthenticated RecursionError DoS in pre-verification payload parse (PyJWKClient.get_signing_key_from_jwt / verify_signature=False) · 30 Sept 2026
- MediumCVE-2026-102270PyJWT: ReDoS vulnerability when calling the `is_pem_format` function. · 30 Sept 2026
- HighCVE-2026-102266PyJWT: PyJWK accepts empty HMAC keys, bypassing PyJWT's empty-key validation · 29 Sept 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.