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.4%, top 73% 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)
- EPSS
- 27.5%
- 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
(1 across 1 ecosystem)
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 10× in last 7d / 65× 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.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 00:18 UTCVendor advisory
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 12:52 UTCVendor advisory
- 2026-07-16 01:25 UTCVendor advisory
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 13:59 UTCVendor advisory
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 14:38 UTCVendor advisory
- 2026-07-14 03:11 UTCVendor advisory
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 04:18 UTCVendor advisory
- 2026-07-12 16:49 UTCVendor advisory
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 05:22 UTCVendor advisory
- 2026-07-11 17:56 UTCVendor advisory
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 06:30 UTCVendor advisory
Show 40 moreShow fewer
- 2026-07-10 19:04 UTCVendor advisory
- 2026-07-10 07:38 UTCVendor advisory
- 2026-07-09 20:12 UTCVendor advisory
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 08:45 UTCVendor advisory
- 2026-07-08 21:19 UTCVendor advisory
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 09:51 UTCVendor advisory
- 2026-07-07 22:25 UTCVendor advisory
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 11:00 UTCVendor advisory
- 2026-07-06 23:05 UTCVendor advisory
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 11:38 UTCVendor advisory
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 00:10 UTCVendor advisory
- 2026-07-05 12:44 UTCVendor advisory
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 01:16 UTCVendor advisory
- 2026-07-04 13:37 UTCVendor advisory
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 02:08 UTCVendor advisory
- 2026-07-03 14:40 UTCVendor advisory
- 2026-07-03 03:13 UTCVendor advisory
- 2026-07-02 15:48 UTCVendor advisory
- 2026-07-02 04:21 UTCVendor advisory
- 2026-07-01 16:55 UTCVendor advisory
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 06:37 UTCEG score recompute▼ 1.20
- 2026-06-30 04:34 UTCNVD updateCVSS v3 → 7.5
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 20:05 UTCEG score recompute
- 2026-06-24 20:03 UTCNVD updatefirst tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
- CVE-2006-10003EG 9.8CRITICAL
- CVE-2015-20107NVD 7.6EG 9.8EPSS 94%HIGH
- CVE-2013-7381EG 9.8CRITICAL
- CVE-2014-0048EG 9.8EPSS 93%CRITICAL
- CVE-2007-4559EG 9.8EPSS 98%CRITICAL
- CVE-2013-3900NVD 5.5EG 9.0 KEVEPSS 99%MEDIUM
- CVE-2013-2094NVD 8.4EG 9.0 KEVEPSS 99%HIGH
- CVE-2014-9356EG 8.6EPSS 91%HIGH
- CVE-2014-5282EG 8.1HIGH
- CVE-2014-8141EG 7.8EPSS 94%HIGH
Same CWE
10 shownCWE-400
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.