Improper Verification of Cryptographic Signature Affecting pyjwt package, versions [2.13.0,2.14.0)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-PYTHON-PYJWT-20245619
- published29 Sept 2026
- disclosed28 Sept 2026
- creditshaffer
Introduced: 28 Sep 2026
NewCVE-2026-102272 (opens in a new tab)How to fix?
Upgrade PyJWT to version 2.14.0 or higher.
Overview
PyJWT is a Python implementation of RFC 7519.
Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature via the prepare_key method in jwt/algorithms.py, where an encoded JWK (such as an RSA public key) is accepted as a valid HMAC secret without rejection. An attacker who knows the target application's RSA public key can supply it as the HMAC secret to forge JWT tokens with arbitrary claims, which a verifier configured with a mixed algorithm set (e.g., algorithms=["HS256", "RS256"]) will accept as valid.
Note: This is only exploitable when the verifier is configured to accept both an asymmetric algorithm (e.g., RS256) and a symmetric HMAC algorithm (e.g., HS256) simultaneously.