CVE-2022-29217
HIGHEPSS 70th pctlDescription
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.
How to fix
This Ubuntu release reached end-of-life on 2023-05-31. Extended security maintenance is available until 2028-04-01.
This Ubuntu release reached end-of-life on 2025-05-31. Extended security maintenance is available until 2030-04-02.
This Ubuntu release reached end-of-life on 2023-05-31. Extended security maintenance is available until 2028-04-01.
This Ubuntu release reached end-of-life on 2023-05-31. Extended security maintenance is available until 2028-04-01.
This Ubuntu release reached end-of-life on 2025-05-31. Extended security maintenance is available until 2030-04-02.
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Exploit Intelligence
Elevated risk: more likely to be exploited than 70% of all known CVEs.
References
Related Vulnerabilities
Other CWE-327 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2013-2566 | Medium | 5.9 | 84% | - | Fix |
| CVE-2015-2808 | Low | 3.7 | 74% | - | Fix |
| CVE-2023-34039 | Critical | 9.8 | 67% | - | Fix |
| CVE-2016-6602 | Critical | 9.8 | 55% | - | - |
| CVE-2014-8687 | Critical | 9.8 | 44% | - | - |
| CVE-2020-13777 | High | 7.4 | 18% | - | Fix |
Common questions
How do I fix CVE-2022-29217?
Published advisories record a fix for 6 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2022-29217 being actively exploited?
Not that we know of. CVE-2022-29217 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 1.4% is the estimated probability that it will be exploited in the next 30 days. That is higher than 70% of all scored CVEs.
How severe is CVE-2022-29217?
CVE-2022-29217 has a CVSS v3 base score of 7.4, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2022-29217 affect?
Published advisories record a fix for python3-jwt (Amazon), python3-jwt+crypto (Amazon), pyjwt (Debian), pyjwt (Ubuntu), and 2 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2022-29217
Markdown
[](https://tridentstack.com/cve/CVE-2022-29217)HTML
<a href="https://tridentstack.com/cve/CVE-2022-29217"><img src="https://tridentstack.com/cve/badge/CVE-2022-29217.svg" alt="CVE-2022-29217"></a>Check your Linux endpoints for this class of vulnerability
TridentStack Control continuously scans Linux endpoints for known vulnerabilities and deploys the fixes from the same console. 200 endpoints free forever, no credit card.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-06-17.