Debian Pyjwt vulnerabilities
5 known vulnerabilities affecting debian/pyjwt.
Total CVEs
5
CISA KEV
0
Public exploits
0
Exploited in wild
0
Severity breakdown
HIGH3LOW2
Vulnerabilities
Page 1 of 1
CVE-2026-32597HIGHCVSS 7.52026
CVE-2026-32597 [HIGH] CVE-2026-32597: pyjwt - PyJWT is a JSON Web Token implementation in Python. Prior to 2.12.0, PyJWT does ...
PyJWT is a JSON Web Token implementation in Python. Prior to 2.12.0, PyJWT does not validate the crit (Critical) Header Parameter defined in RFC 7515 §4.1.11. When a JWS token contains a crit array listing extensions that PyJWT does not understand, the library accepts the token instead of rejecting it. This violates the MUST requirement in the RFC. This vulnerability
debian
CVE-2025-45768LOWCVSS 7.02025
CVE-2025-45768 [HIGH] CVE-2025-45768: pyjwt - pyjwt v2.10.1 was discovered to contain weak encryption. NOTE: this is disputed ...
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).
Scope: local
bookworm: open
bullseye: open
forky: open
sid: open
trixie: open
debian
CVE-2024-53861LOWCVSS 2.22024
CVE-2024-53861 [LOW] CVE-2024-53861: pyjwt - pyjwt is a JSON Web Token implementation in Python. An incorrect string comparis...
pyjwt is a JSON Web Token implementation in Python. An incorrect string comparison is run for `iss` checking, resulting in `"acb"` being accepted for `"_abc_"`. This is a bug introduced in version 2.10.0: checking the "iss" claim changed from `isinstance(issuer, list)` to `isinstance(issuer, Sequence)`. Since str is a Sequnce, but not a list, `in` is also used for stri
debian
CVE-2022-29217HIGHCVSS 7.4fixed in pyjwt 2.4.0-1 (bookworm)2022
CVE-2022-29217 [HIGH] CVE-2022-29217: pyjwt - PyJWT is a Python implementation of RFC 7519. PyJWT supports multiple different ...
PyJWT is a Python implementation of RFC 7519. PyJWT supports multiple different JWT signing algorithms. With JWT, an attacker submitting the JWT token can choose the used signing algorithm. The PyJWT library requires that the application chooses what algorithms are supported. The application can specify `jwt.algorithms.get_default_algorithms()` to get support for all
debian
CVE-2017-11424HIGHCVSS 7.5fixed in pyjwt 1.4.2-1.1 (bookworm)2017
CVE-2017-11424 [HIGH] CVE-2017-11424: pyjwt - In PyJWT 1.5.0 and below the `invalid_strings` check in `HMACAlgorithm.prepare_k...
In PyJWT 1.5.0 and below the `invalid_strings` check in `HMACAlgorithm.prepare_key` does not account for all PEM encoded public keys. Specifically, the PKCS1 PEM encoded format would be allowed because it is prefaced with the string `-----BEGIN RSA PUBLIC KEY-----` which is not accounted for. This enables symmetric/asymmetric key confusion attacks against users using
debian