jpadilla pyjwt up to 2.12.x JWKS Endpoint PyJWKClient.get_signing_key cleanup
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.7 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in jpadilla pyjwt up to 2.12.x. Affected is the function PyJWKClient.get_signing_key of the component JWKS Endpoint. Executing a manipulation can lead to cleanup.
This vulnerability is tracked as CVE-2026-48524. The attack can be launched remotely. No exploit exists.
Upgrading the affected component is advised.
Details
A vulnerability has been found in jpadilla pyjwt up to 2.12.x and classified as problematic. This vulnerability affects the function PyJWKClient.get_signing_key of the component JWKS Endpoint. The manipulation with an unknown input leads to a cleanup vulnerability. The CWE definition for the vulnerability is CWE-460. The product does not clean up its state or incorrectly cleans up its state when an exception is thrown, leading to unexpected state or control flow. As an impact it is known to affect availability. CVE summarizes:
PyJWT is a JSON Web Token implementation in Python. Prior to 2.13.0, PyJWKClient.get_signing_key() forces a fresh HTTP request to the JWKS endpoint for every JWT with an unknown kid value, with no rate limiting. Since kid comes from the unverified token header, an attacker can trigger unlimited outbound requests. The vulnerability surfaces only when a JWKS fetch fails; an attacker can attempt to provoke that with sustained unknown-kid traffic, but the outcome depends on upstream JWKS-endpoint behavior (rate limiting, transient errors) which is beyond the attacker's control. This vulnerability is fixed in 2.13.0.
The advisory is shared for download at github.com. This vulnerability was named CVE-2026-48524 since 05/21/2026. The exploitation appears to be difficult. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available.
Upgrading to version 2.13.0 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
Website
- Product: https://github.com/jpadilla/pyjwt/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.7VulDB Meta Temp Score: 3.7
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 3.7
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: CleanupCWE: CWE-460 / CWE-459
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: pyjwt 2.13.0
Timeline
05/21/2026 CVE reserved05/28/2026 Advisory disclosed
05/28/2026 VulDB entry created
05/28/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-fhv5-28vv-h8m8
Status: Confirmed
CVE: CVE-2026-48524 (🔒)
GCVE (CVE): GCVE-0-2026-48524
GCVE (VulDB): GCVE-100-366772
Entry
Created: 05/28/2026 18:43Changes: 05/28/2026 18:43 (65)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.