Skip to main content
VulnerabilityPublished

CVE-2026-102272: jpadilla pyjwt · Improper Verification of Cryptographic Signature

Affects jpadilla pyjwtSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.4 High : upgrade to 2.14.0 soon.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score
7.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.14.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade jpadilla pyjwt to 2.14.0.

Affected software

ProductAffectedFixed in
jpadillapyjwtAffected
  • >=2.13.0 <2.14.0
Fixed in
  • 2.14.0
PyPIpyjwtpkg:pypi/pyjwtOther threatsAffected
  • >=2.13.0 <2.14.0
Fixed in
  • 2.14.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix for this vulnerability has been committed but not yet released. Users should monitor the vendor's official channels for the release of the patched version and upgrade promptly once available. Until then, avoid accepting both HS256 and RS256 algorithms simultaneously or implement additional validation to mitigate the risk.

Description

PyJWT version 2.13.0 has a vulnerability in its cryptographic signature verification due to improper handling of UTF-8 BOM prefixes in JSON Web Key detection. This flaw allows attackers who know the RSA public key to forge JWT tokens with arbitrary claims if the verifier accepts both HS256 and RS256 algorithms. The issue causes an RSA public key to be misinterpreted as an HMAC secret, resulting in complete authentication and authorization bypass. A fix has been committed but not yet released as of the advisory date.

References

Community reviews

Loading reviews…