Skip to main content
VulnerabilityPublished

CVE-2026-59924: lepture mistune · Path Traversal

Affects lepture mistuneSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium : upgrade to 3.3.0 when convenient.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.3.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade lepture mistune to 3.3.0.

Affected software

ProductAffectedFixed in
lepturemistuneAffected
  • <3.3.0
Fixed in
  • 3.3.0
PyPImistunepkg:pypi/mistuneOther threatsAffected
  • <3.3.0
Fixed in
  • 3.3.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Mistune to version 3.3.0 or later, where this path traversal vulnerability is fixed. No other mitigation or workaround is indicated in the available data.

Description

Mistune is a Python Markdown parser with renderers and plugins. Prior to 3.3.0, Include.parse() joins and normalizes user-supplied include paths without verifying that the result remains within the intended markdown directory, allowing crafted include paths to access files outside that directory when markdown files are processed using md.read(). This issue is fixed in version 3.3.0.

References

Community reviews

Loading reviews…