Skip to main content
VulnerabilityPublished

CVE-2026-121437: lepture mistune · Inefficient Algorithmic Complexity

Affects lepture mistuneSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 3.3.4 soon.

Data as of 3 Nov 2026, 14:58 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.7
CNA (VulnCheck)CVSS 3.17.5
Patch
Available – fixed in 3.3.4
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Nov 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 3 Nov 2026.

What to do

Upgrade lepture mistune to 3.3.4.

Affected software

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

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.4 or later, where this vulnerability is fixed. No other mitigation is indicated or required.

Description

Mistune versions from 3.3.0 up to but not including 3.3.4 contain a denial of service vulnerability due to inefficient algorithmic complexity in emphasis delimiter processing. Remote attackers can exploit this by submitting small markdown documents with repeated patterns, causing a quadratic-time loop that exhausts CPU resources and stalls workers. The issue is fixed in version 3.3.4.

References

Community reviews

Loading reviews…