CVE-2022-29217 | Key confusion through non-blocklisted public key formats in PyJWT

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-24 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-29217 is rated Moderate Risk (51.5/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.42%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-29217

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-09 0.31% 0.42% +0.11%
2 2026-03-04 0.63% 0.31% -0.32%
3 2026-03-01 — 0.63% —

Full EPSS history (36 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-29217

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.4 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 2.2 5.2 [email protected]
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:N/I:P/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2022-29217

GitHub Security Advisory for CVE-2022-29217

GHSA-ffqj-6fqr-9h24 · Severity: high · Ecosystem: pip — Key confusion through non-blocklisted public key formats

OS Trackers for CVE-2022-29217

vendor priority summary link
alpine high CVE-2022-29217: 1 source package rows (py3-jwt); 7 state rows across 7 repos (3.17-community, 3.18-community, 3.19-community, 3.20-community, 3.21-community, 3.22-community, edge-community); fixed 7, open 0. https://security.alpinelinux.org/vuln/CVE-2022-29217
debian unimportant CVE-2022-29217 unimportant priority: Debian including 1 source packages (pyjwt), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-29217
redhat medium — https://access.redhat.com/security/cve/CVE-2022-29217
suse high CVE-2022-29217 severity important: SUSE including 255 source package names (1.10.1.16.4.5.348:python3-PyJWT-2.4.0-150200.3.6.2, 3.8.0.0.3.2.652:python3-PyJWT-2.4.0-150200.3.6.2, …), 487 product×package rows across 248 product lines (Container ses/7.1/cephcsi/cephcsi, Container ses/7.1/rook/ceph, … (248 product lines)): Fixed 350, Known Affected 131, Will Not Fix 5, Known Not Affected 1. https://www.suse.com/security/cve/CVE-2022-29217/
ubuntu medium CVE-2022-29217 medium priority: Ubuntu including 1 source packages (pyjwt), 7 status rows across 7 suites (bionic, focal, impish, jammy, trusty, upstream, xenial): released 4, DNE 1, ignored 1, not-affected 1. https://ubuntu.com/security/CVE-2022-29217

Affected software / configurations for CVE-2022-29217

Vendor Product Version Raw CPE
pyjwt_project pyjwt >= 1.5.0, < 2.4.0 cpe:2.3:a:pyjwt_project:pyjwt:*:*:*:*:*:*:*:*
fedoraproject fedora 35 cpe:2.3:o:fedoraproject:fedora:35:*:*:*:*:*:*:*
fedoraproject fedora 36 cpe:2.3:o:fedoraproject:fedora:36:*:*:*:*:*:*:*

References for CVE-2022-29217

cvelogic Threat Intelligence