Approved changes feed: RSS · Atom

cpe:2.3:a:pyjwt_project:pyjwt:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorPyjwt Project (a29c9aac-0bed-50ea-9640-6ee50b197df1)
ProductPyjwt (ba73b7dc-dee7-53e3-b202-d14980a80562)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:deb/debian/pyjwt purl2cpe 2026-06-01 10:15:46.613845
pkg:deb/ubuntu/pyjwt purl2cpe 2026-06-01 10:15:46.613847
pkg:github/jpadilla/pyjwt purl2cpe 2026-06-01 10:15:46.613849
pkg:pypi/pyjwt purl2cpe 2026-06-01 10:15:46.613850
pkg:rpm/opensuse/python-pyjwt purl2cpe 2026-06-01 10:15:46.613852

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-32597 vulnerable 2026-06-08 07:57:17.733031 PyJWT accepts unknown `crit` header extensions (RFC 7515 §4.1.11 MUST violation)
HIGH (7.5)
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 is fixed in 2.12.0.
Published: 2026-03-12T21:41:50.427Z
Updated: 2026-09-10T12:05:06.316Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2022-29217 vulnerable 2026-06-08 05:42:47.359412 Key confusion through non-blocklisted public key formats in PyJWT
HIGH (7.4)
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 algorithms, or specify a single algorithm. The issue is not that big as `algorithms=jwt.algorithms.get_default_algorithms()` has to be used. Users should upgrade to v2.4.0 to receive a patch for this issue. As a workaround, always be explicit with the algorithms that are accepted and expected when decoding.
Published: 2022-05-24T14:10:10.000Z
Updated: 2025-04-23T18:22:46.326Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2017-11424 vulnerable 2026-06-08 05:08:37.572206 Details available
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 the PKCS1 PEM encoded public keys, which would allow an attacker to craft JWTs from scratch.
Published: 2017-08-24T16:00:00.000Z
Updated: 2024-08-05T18:12:39.550Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.