CVE-2026-48524Disclosure(pyjwt_project / pyjwt)

LOWCVSS 3.7 · LOW

Signal is active with 1 mentions in latest observed window

Immediate actions

Patch pyjwt_project pyjwt systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

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.

pyjwt_project CVEs Back to dashboard

0.5/ 10 priority

Sources & remediation

Vendor / third-party advisories

https://github.com/jpadilla/pyjwt/security/advisories/GHSA-fhv5-28vv-h8m8

Weakness type (CWE)

CWE-460CWE-755

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

pyjwt

Threat summary

Patch or workaround signal is available
2 mentions across 2 observed days
Momentum state: stable

What's happening

Patch or workaround mentioned in 1 signal
Technical details provided in 2 signals
Disclosure: 1 classified signal
Peaked 1d ago at 1 mentions (2026-06-15); latest day: 1
2 total mentions across 2 days

Affected systems

Vendors

pyjwt_project

Products

pyjwt

Deep dive

Activity timeline2 mentions / 2d

Signal classification2 categories

Disclosure

150.0%

Patch

150.0%

Referenced assets2 URLs

By indicator

Classification over time

Date	Total	Labels

2026-06-15	1	Disclosure1
2026-08-08	1	Patch1

Full discourse2 posts

Windows Forum@windowsforum40d
Patch
🔐 PyJWT 2.13.0 fixes the cache wipe, not the JWKS flood: every bogus kid can still trigger a remote key request. Upgrade—and rate-limit auth traffic before login becomes a DDoS button. https://windowsforum.com/security-alerts.84/cve-2026-48524-pyjwt-2-13-0-fixes-cache-wipes-not-jwks-floods.442035/?utm_source=x&utm_medium=social&utm_campaign=news_node84 #Pyjwt #Cve202648524 #JwksSecurity #WindowsPython https://t.co/GBsyPvgEQt
Post summary
The tweet highlights that PyJWT 2.13.0 fixes cache wipe issues but leaves the JWKS flood problem unresolved, recommending upgrading the library and rate‑limiting authentication traffic as mitigations.
0000059
1.3K followersView on X
DailyCVE@dailycve94d
Disclosure
🔵 PyJWT (PyJWKClient), Unbounded JWKS Endpoint Requests, #CVE-2026-48524 (Low) -DC-Jun2026-419 https://dailycve.com/pyjwt-pyjwkclient-unbounded-jwks-endpoint-requests-cve-2026-48524-low-dc-jun2026-419/
Post summary
This entry announces CVE-2026-48524, a low‑severity vulnerability in PyJWT's PyJWKClient involving unbounded JWKS endpoint requests, but provides no exploitation details or patch information.
0000032
212 followersView on X

CPE platform detail1 entries

Part:

Vendor:

Product:

Version:

Target SW:

Target HW:

1 of 1 entries

Part	Vendor	Product	Version	Target SW	Target HW
App	pyjwt_project	pyjwt	-	-	-

Explore more

Back to dashboard pyjwt_project CVEs pyjwt vulnerabilities