Vulnerability in pyjwt (CVE-2026-48524)
Summary
Vulnerability in pyjwt (CVE-2026-48524). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.13.0 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-48524 has been found in pyjwt.
Risk of unauthorized operations or information disclosure. CVSS score: 3.7/10.
What to do: upgrade pyjwt to 2.13.0 or later.
If unsure, ask your IT team or search "pyjwt CVE-2026-48524" on the vendor's site.
CVE-2026-48524 (pyjwt) — CWE-460 / CVSS v3 3.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.13.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-460) exists in pyjwt.
Check the vendor advisory for the affected versions of pyjwt.
Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.
Update to 2.13.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'pyjwt' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'pyjwt' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
pyjwtを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade pyjwt to 2.13.0ステージング環境で 2.13.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- BellSoft Alpaquita BELL-CVE-2026-48524 py3-jwt Fixed in: 2.13.0-r0
- Debian DEBIAN-CVE-2026-48524 pyjwt
- Ubuntu UBUNTU-CVE-2026-48524 pyjwt
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- web github.com
- web github.com
- web github.com