Mistune is a Python Markdown parser with renderers and plugins. Prior to 3.3.0, Mistune is vulnerable to a CPU exhaustion DoS due to superlinear (approximately O(n²)) behavior in parse_link_text. When parsing Markdown containing many consecutive [ characters, parse_link_text repeatedly scans the input using a regex search inside a loop. Each iteration re-scans a large portion of the remaining string, resulting in quadratic-time behavior. An attacker-controlled Markdown input can therefore trigger excessive CPU usage with a very small payload. This vulnerability is fixed in 3.3.0.
CVE-2026-49851
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 53% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 1%
- EPSS %ILE
- 47%
- KEV
- Not listed
Published
June 24, 2026
Last Modified
July 15, 2026
Advisory Details (1)
Auto-updated Jun 24, 2026Potential DoS via quadratic-time parsing in parse_link_text · Advisory · lepture/mistune · GitHub
https://github.com/lepture/mistune/security/advisories/GHSA-qcq2-496w-v96pVendor Advisories for CVE-2026-49851(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(3 across 3 ecosystems)
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| mistune | 3.1.3-1, 3.1.4-1 | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| mistune | 3.1.3-1, 3.1.4-1 | — | — |
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| mistune | 0.1.0 ... 3.2.1 (51 versions) | 3.3.0 | — |
Weakness Classification(4)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 21× in last 7d / 101× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 174 total refreshes for this CVE.
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 00:46 UTCEG score recompute
- 2026-08-25 00:46 UTCVendor advisory
- 2026-08-24 13:19 UTCEG score recompute
- 2026-08-24 13:19 UTCVendor advisory
- 2026-08-23 21:56 UTCVendor advisory
- 2026-08-23 10:28 UTCEG score recompute
- 2026-08-23 10:28 UTCVendor advisory
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 22:54 UTCVendor advisory
- 2026-08-22 11:28 UTCEG score recompute
- 2026-08-22 11:28 UTCVendor advisory
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 06:12 UTCEG score recompute
- 2026-08-21 06:12 UTCVendor advisory
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 18:40 UTCVendor advisory
- 2026-08-20 07:15 UTCEG score recompute
- 2026-08-20 07:15 UTCVendor advisory
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 13:30 UTCVendor advisory
- 2026-08-19 01:55 UTCEG score recompute
- 2026-08-19 01:55 UTCVendor advisory
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 15:09 UTCEG score recompute
Show 75 moreShow fewer
- 2026-08-17 15:09 UTCVendor advisory
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 03:42 UTCVendor advisory
- 2026-08-16 16:16 UTCEG score recompute
- 2026-08-16 16:16 UTCVendor advisory
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 04:49 UTCEG score recompute
- 2026-08-16 04:49 UTCVendor advisory
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 17:23 UTCVendor advisory
- 2026-08-15 05:57 UTCEG score recompute
- 2026-08-15 05:57 UTCVendor advisory
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 18:30 UTCVendor advisory
- 2026-08-14 07:04 UTCEG score recompute
- 2026-08-14 07:04 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 19:38 UTCVendor advisory
- 2026-08-13 08:12 UTCVendor advisory
- 2026-08-12 20:46 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 09:20 UTCVendor advisory
- 2026-08-11 21:54 UTCEG score recompute
- 2026-08-11 21:54 UTCVendor advisory
- 2026-08-11 10:28 UTCEG score recompute
- 2026-08-11 10:28 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 00:08 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 12:43 UTCVendor advisory
- 2026-08-09 01:17 UTCEG score recompute
- 2026-08-09 01:17 UTCVendor advisory
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 13:51 UTCVendor advisory
- 2026-08-08 02:25 UTCEG score recompute
- 2026-08-07 03:33 UTCVendor advisory
- 2026-08-06 16:08 UTCEG score recompute
- 2026-08-06 16:08 UTCVendor advisory
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 04:41 UTCEG score recompute
- 2026-08-06 04:41 UTCVendor advisory
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 02:36 UTCEG score recompute
- 2026-08-05 02:36 UTCVendor advisory
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 15:10 UTCEG score recompute
- 2026-08-04 15:10 UTCVendor advisory
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-03 14:02 UTCEG score recompute
- 2026-08-03 14:02 UTCVendor advisory
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-03 00:55 UTCVendor advisory
- 2026-08-02 13:29 UTCEG score recompute
- 2026-08-02 13:29 UTCVendor advisory
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-02 02:03 UTCVendor advisory
- 2026-08-01 14:37 UTCEG score recompute
- 2026-08-01 14:37 UTCVendor advisory
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-08-01 03:11 UTCVendor advisory
- 2026-07-31 14:54 UTCVendor advisory
- 2026-07-31 03:25 UTCEG score recompute
- 2026-07-31 03:25 UTCVendor advisory
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 14:51 UTCEG score recompute
- 2026-07-30 14:51 UTCVendor advisory
- 2026-07-30 02:11 UTCEG score recompute
- 2026-07-30 02:11 UTCVendor advisory
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 12:09 UTCVendor advisory
- 2026-07-29 00:43 UTCEG score recompute
- 2026-07-29 00:43 UTCVendor advisory
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-28 05:47 UTCVendor advisory
- 2026-07-27 17:33 UTCEG score recompute
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-400 · CWE-770
- CVE-2004-1464NVD 5.9EG 9.0 KEVEPSS p91CRITICAL
- CVE-2010-3705EG 8.3HIGH
- CVE-2006-1364NVD 7.5EG 8.2EPSS p99HIGH
- CVE-2008-5180NVD 5.3EG 7.9EPSS p99HIGH
- CVE-2012-0024EG 7.8HIGH
- CVE-2011-3192EG 7.8EPSS p100HIGH
- CVE-2010-4686EG 7.8HIGH
- CVE-2010-4671EG 7.8HIGH
- CVE-2009-2054EG 7.8HIGH
- CVE-2009-2726EG 7.8EPSS p93HIGH
Frequently asked(5)
What is CVE-2026-49851?
When was CVE-2026-49851 disclosed?
Is CVE-2026-49851 actively exploited?
What is the CVSS score of CVE-2026-49851?
How do I remediate CVE-2026-49851?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49851
Is Your Infrastructure Affected by CVE-2026-49851?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.