← Back
CVE-2026-59924
medium
CVSS 5.9
Path Traversal in mistune (CVE-2026-59924)
Summary
path traversal in mistune (CVE-2026-59924). Confidential information can be exposed externally. Exploitable via ``Include``. Mitigation: upgrade to `3.3.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-59924** has been found in mistune.
Attackers can target a specific entry point like ``Include`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.9/10.
What to do: upgrade mistune to **3.3.0** or later.
If unsure, ask your IT team or search "mistune CVE-2026-59924" on the vendor's site.
CVE-2026-59924 (mistune) — CWE-22 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `Include`
Patched: `3.3.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.
❓ What is the problem
**Path traversal** (CWE-22) exists in mistune. Attackers reach the vulnerable code path via ``Include`` without authentication.
📍 Affected scope
mistune — . Attack surface: `Include`.
🔥 Severity
Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally
🔧 How to fix
Update to **3.3.0**.
🛡️ 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 'mistune' .` 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 'mistune' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `mistune` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade mistune to 3.3.0ステージング環境で 3.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
mistune
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3.0"}]}]
References
- web https://github.com/lepture/mistune/commit/1bef343ade163fc3bb95572b15be720084cdb993
- web https://github.com/lepture/mistune/releases/tag/v3.3.0
- web https://github.com/lepture/mistune/security/advisories/GHSA-r4rv-85jg-w4mf
- web https://nvd.nist.gov/vuln/detail/CVE-2026-59924
- web https://github.com/pypa/advisory-database/tree/main/vulns/mistune/PYSEC-2026-2212.yaml
- web https://github.com/advisories/GHSA-r4rv-85jg-w4mf