Skip to main content
VulnerabilityPublished

CVE-2026-59923: lepture mistune · Cross-site Scripting

Affects lepture mistuneSource CVE Database V5

0
Compare

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

Data as of 20 Nov 2026, 17:35 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 29% 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:L/PR:N/UI:R/S:C/C:L/I:L/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 to Mistune version 3.3.0 or later, where the vulnerability is fixed. Patch status is confirmed by the version fix note. No other mitigations are specified or required.

Description

Mistune is a Python Markdown parser with renderers and plugins. Prior to 3.3.0, HTMLRenderer.safe_url() does not block percent-encoded javascript URIs, allowing attacker-supplied Markdown links or images to bypass URL protections and execute script in rendered HTML. This issue is fixed in version 3.3.0.

References

Community reviews

Loading reviews…