Home/CVE/PyJWT is a Python implementation of RFC 7519. PyJWT supports multiple different JWT signing algorithms. With JWT, an att
CVE
CVE-2022-29217
PyJWT is a Python implementation of RFC 7519. PyJWT supports multiple different JWT signing algorithms. With JWT, an att
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.
HIGH · CVSS 7.4
EPSS 0.00422
Act now
- Public exploit or PoC is available
- CVSS base score ≥ 7.0
Sigma rules0
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2022-29217, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
◆
ATT&CK techniques
2Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.
▤ Build a SIEM detection for these techniques▤
CAPEC attack patterns
7Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.
CAPEC-CAPEC-20 · Encryption Brute Forcing CAPEC-CAPEC-459 · Creating a Rogue Certification Authority Certificate CAPEC-CAPEC-473 · Signature Spoof CAPEC-CAPEC-475 · Signature Spoofing by Improper Validation CAPEC-CAPEC-608 · Cryptanalysis of Cellular Encryption CAPEC-CAPEC-614 · Rooting SIM Cards CAPEC-CAPEC-97 · Cryptanalysis
⬡
Weakness Classification
▤
Affected Products & Versions
2pyjwt project pyjwt>= 1.5.0 and < 2.4.0
fedoraproject fedoraall versions
▤
Affected Packages
4Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.
PyPI
pyjwt
HIGH
fixed in 2.4.0
Ubuntu:18.04:LTS
pyjwt
fixed in 1.5.3+ds1-1ubuntu0.1
Ubuntu:20.04:LTS
pyjwt
fixed in 1.7.1-2ubuntu2.1
Ubuntu:22.04:LTS
pyjwt
fixed in 2.3.0-1ubuntu0.1
⚠
Public Exploits & PoCs
6These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted.
📦
Fixed versions by distribution
6The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
alpine edgepy3-jwt fixed in 2.4.0-r0
alpine v3.19py3-jwt fixed in 2.4.0-r0
alpine v3.20py3-jwt fixed in 2.4.0-r0
suse sle15python2-PyJWT fixed in 0:1.7.1-150100.6.7.1
suse sle15python3-PyJWT fixed in 0:1.7.1-150200.3.3.1
suse sle15python311-PyJWT fixed in 0:2.8.0-150400.8.3.1
▣
Scoring & Timeline
7.4
HIGH · CVSS v3.1 · [email protected]
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
SSVC triage · cisa-vulnrichment
Exploitation
none
Automatable
no
Technical impact
total
SSVC asks the questions that actually drive patch urgency: is it being exploited, can attacks be automated, and how total is the impact.
⚑
Vendor Advisories
14suse-csafopenSUSE-SU-2025:14987-1
suse-csafSUSE-SU-2024:2064-1
suse-csafopenSUSE-SU-2024:12139-1
suse-csafopenSUSE-SU-2024:13928-1
🔗
References & Sources
6Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.
https://github.com/jpadilla/pyjwt/commit/9c528670c455b8d948aff95ed50e22940d1ad3fcPatchThird Party Advisory
https://github.com/jpadilla/pyjwt/security/advisories/GHSA-ffqj-6fqr-9h24Issue TrackingThird Party Advisory