Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

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

Noroxi assessment

Priority: Monitor (action score 30/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.3% (FIRST EPSS); higher than 71.5% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: pyjwt (Debian:12) 2.4.0-1; python-PyJWT (openSUSE:Leap 15.3) 1.7.1-150200.3.3.1; python-PyJWT (openSUSE:Leap 15.4) 2.4.0-150200.3.6.2.

Low priority for now. Upgrade to pyjwt (Debian:12) 2.4.0-1; python-PyJWT (openSUSE:Leap 15.3) 1.7.1-150200.3.3.1; python-PyJWT (openSUSE:Leap 15.4) 2.4.0-150200.3.6.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
May 24, 2022
Updated
Jun 17, 2026
EPSS
1.3% · 71th percentile

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.5
CNA · GitHub_M
7.4
0.1 point gap

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-29217

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for pyjwt project records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
pyjwt projectpyjwt
fedoraprojectfedora

Check your site's encryption

This vulnerability is about certificate validation or weak cryptography. The free SSL checker tests your certificate, enabled TLS versions and weak ciphers.

Run the SSL check

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • fedoraproject fedora35
  • fedoraproject fedora36
  • pyjwt project pyjwt1.5.0 and later · before 2.4.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • jpadilla pyjwt

    • >= 1.5.0, < 2.4.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12pyjwtbefore 2.4.0-12.4.0-1
openSUSE:Leap 15.3python-PyJWTbefore 1.7.1-150200.3.3.11.7.1-150200.3.3.1
openSUSE:Leap 15.4python-PyJWTbefore 2.4.0-150200.3.6.22.4.0-150200.3.6.2
openSUSE:Tumbleweedpython-PyJWTbefore 2.10.1-2.12.10.1-2.1
PyPIpyjwtfrom 1.5.0 · before 2.4.02.4.0
SUSE:Linux Enterprise Module for Basesystem 15 SP3python-PyJWTbefore 1.7.1-150200.3.3.11.7.1-150200.3.3.1
SUSE:Linux Enterprise Module for Basesystem 15 SP4python-PyJWTbefore 2.4.0-150200.3.6.22.4.0-150200.3.6.2
SUSE:Linux Enterprise Module for Public Cloud 12python-PyJWTbefore 1.5.3-3.16.11.5.3-3.16.1
SUSE:Linux Enterprise Module for Public Cloud 15python-PyJWTbefore 1.5.3-150000.3.3.11.5.3-150000.3.3.1
SUSE:Linux Enterprise Module for Public Cloud 15 SP1python-PyJWTbefore 1.7.1-150100.6.7.11.7.1-150100.6.7.1

Same product

pyjwt project: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-102268PyJWT: Asymmetric-PEM detection bypass: whitespace/line-ending-mutated public keys skip the HS/asymmetric confusion guard
    36Monitor
  • CVE-2026-102267PyJWT: PyJWKClient follows redirects when fetching JWKS
    36Monitor
  • CVE-2026-102266PyJWK accepts empty HMAC keys, bypassing PyJWT's empty-key validation
    36Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2017-11424Aug 24, 2017 · In PyJWT 1.5.0 and below the `invalid_strings` check in `HMACAlgorithm.prepare_key` does not account for all PEM encoded public keys.
    31Monitor
  • Later →CVE-2024-53861Nov 29, 2024 · Issuer field partial matches allowed in pyjwt
    30Monitor
  • Later →CVE-2025-45768Jul 31, 2025 · pyjwt v2.10.1 was discovered to contain weak encryption.
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:pyjwt2.4.0-1 · Debian:12Package registry (OSV)
opensuse:python-PyJWT1.7.1-150200.3.3.1 · openSUSE:Leap 15.3Package registry (OSV)
PyPI:pyjwt2.4.0Package registry (OSV)
suse:python-PyJWT1.5.3-3.16.1 · SUSE:Linux Enterprise Module for Public Cloud 12Package registry (OSV)
suse:python-PyJWT1.7.1-150200.3.3.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
None

Weakness class (CWE)

CWE-327 · Use of a Broken or Risky Cryptographic Algorithm

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records