Skip to main content
VulnerabilityPublished

CVE-2026-44708: 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.2.1 when convenient.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.2.1
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 26 May 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 29 Oct 2026.

What to do

Upgrade lepture mistune to 3.2.1.

Affected software

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

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.2.1 or later, where this vulnerability is fixed. Since the vulnerability is addressed in this official release, applying this update is the recommended remediation. Patch status is confirmed fixed in 3.2.1. No additional mitigations are specified or required.

Description

Mistune is a Python Markdown parser with renderers and plugins. Prior to 3.2.1, the mistune math plugin renders inline math ($...$) and block math ($$...$$) by concatenating the raw user-supplied content directly into the HTML output without any HTML escaping. This occurs even when the parser is explicitly created with escape=True, which is supposed to guarantee that all user-controlled text is sanitised before reaching the DOM. This vulnerability is fixed in 3.2.1.

References

Community reviews

Loading reviews…