Vulnerability in mistune (CVE-2026-59929)
Summary
Vulnerability in mistune (CVE-2026-59929). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.3.0 or later.
Original description
The description as published by the source.
Mistune is a Python Markdown parser with renderers and plugins. Prior to 3.3.0, the safe_url filter in src/mistune/renderers/html.py blocks only javascript:, vbscript:, file:, and data: schemes, allowing legacy or chained schemes such as feed:, view-source:, jar:, livescript:, mocha:, ms-its:, mk:, and res: to reach rendered href and src attributes and potentially execute script in affected user agents. This issue is fixed in version 3.3.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-59929 has been found in mistune.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade mistune to 3.3.0 or later.
If unsure, ask your IT team or search "mistune CVE-2026-59929" on the vendor's site.
CVE-2026-59929 (mistune) — CWE-184 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
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.
A vulnerability (CWE-184) exists in mistune.
Check the vendor advisory for the affected versions of mistune.
Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure.
Update to 3.3.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 'mistune' . 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 'mistune' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mistuneを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade mistune to 3.3.0ステージング環境で 3.3.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
- Ubuntu UBUNTU-CVE-2026-59929 mistune
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com
- web github.com
- web github.com