← Back
CVE-2024-53861
Vulnerability in pyjwt (CVE-2024-53861)
Summary
vulnerability in pyjwt (CVE-2024-53861). Risk of unauthorized operations or information disclosure. Exploitable via ``iss``. Mitigation: upgrade to `2.10.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-53861** has been found in pyjwt.
Attackers can target a specific entry point like ``iss`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade pyjwt to **2.10.1** or later.
If unsure, ask your IT team or search "pyjwt CVE-2024-53861" on the vendor's site.
CVE-2024-53861 (pyjwt) — CWE-697 /
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `iss`
Patched: `2.10.1` — 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.
❓ What is the problem
**A vulnerability** (CWE-697) exists in pyjwt. Attackers reach the vulnerable code path via ``iss`` without authentication.
📍 Affected scope
pyjwt — . Attack surface: `iss`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.10.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade pyjwt to 2.10.1ステージング環境で 2.10.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
pyjwt
[{"type":"ECOSYSTEM","events":[{"introduced":"2.10.0"},{"fixed":"2.10.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-53861
- advisory https://github.com/advisories/GHSA-75c5-xw7c-p5pm
- package https://github.com/jpadilla/pyjwt
- package https://pypi.org/project/pyjwt
- web https://github.com/jpadilla/pyjwt/security/advisories/GHSA-75c5-xw7c-p5pm
- web https://github.com/jpadilla/pyjwt/commit/1570e708672aa9036bc772476beae8bfa48f4131#diff-6893ad4a1c5a36b8af3028db8c8bc3b62418149843fc382faf901eaab008e380R366
- web https://github.com/jpadilla/pyjwt/commit/33022c25525c1020869c71ce2a4109e44ae4ced1