CVE-2026-33079
Received Received - Intake
Mistune ReDoS Vulnerability in Link Title Parsing

Publication date: 2026-05-06

Last updated on: 2026-05-06

Assigner: GitHub, Inc.

Description
In versions 3.0.0a1 through 3.2.0 of Mistune, there is a ReDoS (Regular Expression Denial of Service) vulnerability in `LINK_TITLE_RE` that allows an attacker who can supply Markdown for parsing to cause denial of service. The regular expression used for parsing link titles contains overlapping alternatives that can trigger catastrophic backtracking. In both the double-quoted and single-quoted branches, a backslash followed by punctuation can be matched either as an escaped punctuation sequence or as two ordinary characters, creating an ambiguous pattern inside a repeated group. If an attacker supplies Markdown containing repeated ! sequences with no closing quote, the regex engine explores an exponential number of backtracking paths. This is reachable through normal Markdown parsing of inline links and block link reference definitions. A small crafted input can therefore cause significant CPU consumption and make applications using Mistune unresponsive.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-06
Last Modified
2026-05-06
Generated
2026-05-07
AI Q&A
2026-05-06
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
lepture mistune From 3.0.0a1 (inc) to 3.2.0 (inc)
mistune mistune From 3.0.0a1 (inc) to 3.2.0 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-1333 The product uses a regular expression with an inefficient, possibly exponential worst-case computational complexity that consumes excessive CPU cycles.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability exists in versions 3.0.0a1 through 3.2.0 of Mistune, a Markdown parser. It is a Regular Expression Denial of Service (ReDoS) issue in the LINK_TITLE_RE regular expression used for parsing link titles.

The problem arises because the regex contains overlapping alternatives that cause catastrophic backtracking. Specifically, in both double-quoted and single-quoted branches, a backslash followed by punctuation can be interpreted in two ways, creating ambiguity inside a repeated group.

An attacker who can supply Markdown input can craft a string with repeated exclamation marks and no closing quote, causing the regex engine to explore an exponential number of backtracking paths. This leads to significant CPU consumption and can make applications using Mistune unresponsive.


How can this vulnerability impact me? :

This vulnerability can cause denial of service by making applications that use Mistune unresponsive due to excessive CPU consumption.

An attacker can exploit this by supplying specially crafted Markdown input that triggers the problematic regular expression, leading to catastrophic backtracking and resource exhaustion.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability causes a denial of service by making applications using Mistune unresponsive due to excessive CPU consumption triggered by crafted Markdown input.

While the CVE description and resources do not explicitly mention compliance with standards such as GDPR or HIPAA, denial of service vulnerabilities can indirectly impact compliance by affecting system availability and reliability.

Standards like GDPR and HIPAA require organizations to ensure availability and integrity of systems processing personal or sensitive data. A denial of service vulnerability could lead to service outages or interruptions, potentially violating these requirements.

Therefore, this vulnerability could negatively affect compliance with such regulations by risking system availability, especially in environments where Mistune is used to parse Markdown input in critical applications.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by testing the Markdown parser with crafted inputs that contain repeated backslash-punctuation sequences without closing quotes, which trigger the vulnerable regular expression to cause excessive CPU consumption.

Specifically, you can supply Markdown inputs with repeated exclamation marks or similar patterns in inline links or block link reference definitions to observe if the parser becomes unresponsive or consumes high CPU.

While no specific commands are provided in the resources, a practical approach is to create a test Markdown file containing a payload such as repeated '! sequences without closing quotes and then run the application or parser to monitor CPU usage and responsiveness.


What immediate steps should I take to mitigate this vulnerability?

The immediate mitigation step is to update the Mistune Markdown parser to a version later than 3.2.0 where the vulnerable regular expression `LINK_TITLE_RE` has been fixed.

The fix involves modifying the regex to exclude backslashes from the catch-all character class, which eliminates the ambiguous pattern causing catastrophic backtracking.

Until an update can be applied, consider restricting or sanitizing Markdown input to prevent maliciously crafted link titles that could trigger the vulnerability.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart