CVE-2026-59930 json
Mistune toc / TableOfContents directive: heading IDs use predictable `toc_N` numbering with no slugification, allowing collision with attacker-controlled `id="toc_N"` content
published 4mo ago modified 17d ago also EUVD-2026-42330 , GHSA-2hm2-hc3v-44h9 , PYSEC-2026-2218
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
Mistune is a Python Markdown parser with renderers and plugins. Prior to 3.3.0, the toc plugin and TableOfContents directive generate heading IDs as predictable toc_N values without slugifying the heading text, allowing attacker-controlled id="toc_N" content to collide with generated anchors and redirect same-page navigation, CSS selectors, or JavaScript handlers. This issue is fixed in version 3.3.0.
Patch / fix
- pypi mistune 3.3.0
- mistune_project mistune 3.3.0
- python-mistune SLES for SAP applications 16.0, SLES 16.0 3.1.3-160000.5.1
suse advisories SUSE-SU-2026:22655-1
- python-mistune openSUSE Leap 16.0 3.1.3-160000.5.1
opensuse advisories openSUSE-SU-2026:21339-1
Is CVE-2026-59930 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-59930 updated cvss 4.3
mistune: Mistune: Same-page navigation redirection due to predictable heading IDs
-
Red Hat Migration Toolkit for Applications 8 mta/mta-solution-server-rhel9 Red Hat OpenShift AI (RHOAI) rhoai/odh-th06-cpu-torch210-py312-rhel9, rhoai/odh-th06-cpu-torch291-py312-rhel9, rhoai/odh-th06-rocm64-torch291-py312-rhel9, rhoai/odh-th06-cuda130-torch210-py312-rhel9, rhoai/odh-th06-cuda130-torch291-py312-rhel9, rhoai/odh-pipeline-runtime-minimal-cpu-py312-rhel9, +16 more Red Hat Satellite 6 satellite/iop-advisor-engine-rhel9affected: workaround, no fix available “There are no known mitigations for this issue.”
-
Red Hat OpenShift Container Platform 4 python-mistune 0.8.3-15.2.el9ocpnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4mo ago
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/lepture/mistune/security/advisories/GHSA-2hm2-hc3v-44h9 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
| GitHub | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
| OSV | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | mistune | <3.3.0 |
3.3.0 |
Affected products
- lepture mistune
Classification
References
-
github.com
/lepture/mistune/commit/c4093c4742ed0d10d9332fb8edb455869b7b581b
web, patch
-
github.com
/lepture/mistune/security/advisories/GHSA-2hm2-hc3v-44h9
exploit, web, third-party-advisory, evidence, advisory
-
github.com
/lepture/mistune/releases/tag/v3.3.0
web, release-notes, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-59930
advisory
-
github.com
/lepture/mistune
package
-
github.com
/pypa/advisory-database/tree/main/vulns/mistune/PYSEC-2026-2218.yaml
web
Sources
- CVE List CVE-2026-59930
- GitHub Advisory GHSA-2hm2-hc3v-44h9
- NVD CVE-2026-59930
- OSV PYSEC-2026-2218
- Maintainer advisory GHSA-2hm2-hc3v-44h9
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of lepture/mistune published their own advisory on GitHub. Reviewed sources take precedence over it.