GHSA-253c-mchw-3w2r: Npm/markdown-it vulnerability
Summary
Two independent quadratic paths in the linkify: true handling. Both are in markdown-it's own code rather than in linkify-it, which stays linear on both payloads.
src/rulescore/linkify.ts calls arrayReplaceAt once per linkified text token, and that rebuilds the whole children array each time. A paragraph of N soft-broken lines is one inline token with about 2N children, so you get N rebuilds over a 2N array. Schema-less emails are what reach it. A http:// link gets consumed by the inline rule first and never arrives as a text token, so those stay linear.
src/rulesinline/linkify.ts runs state.pending.match(SCHEMERE) at every :// in the source. state.pending only gets truncated once a link is actually produced, so an unregistered scheme leaves it growing and every :// rescans the lot.
Proof of concept
Clean install of 15.0.0 from npm, new MarkdownIt({ linkify: true }).render(payload), Node 24.
| N | 5,000 | 10,000 | 20,000 | 40,000 | |---|---|---|---|---| | 'a@b.co\n'.repeat(N), 34KB to 273KB | 1.1s | 4.7s | 19.6s | 89s | | 'a://'.repeat(N), 20KB to 156KB | 0.25s | 0.76s | 3.1s | 15.0s |
Doubling the input roughly quadruples the time in both. With linkify: false the same inputs run in 25 to 131ms and stay flat.
Controls for the first one, all at N=20000: putting every email in a single text token ('a@b.co ') takes 0.59s, one email per paragraph ('a@b.co\n\n') takes 0.64s, and soft-broken lines with nothing linkifiable take 42ms. So it needs many children AND many of them linkifying. For the second, replaying just the SCHEMERE calls against the same growing prefixes with no markdown-it involved accounts for 11.7s of the 15s.
Ordinary prose does it too. 'ping a@b.co ok\n'.repeat(20000) is 293KB and takes 31s.
Caveat
linkify is off by default, so this only reaches apps that turn it on.
Impact
Availability only. A few hundred KB of fairly ordinary markdown pins one core for tens of seconds, and because it's quadratic it degrades quickly with size. Nothing is read, written or executed.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/markdown-itto a version that resolves this vulnerability.Fixed in 14.3.1 - Upgrade
Upgrade
npm/markdown-itto a version that resolves this vulnerability.Fixed in 15.0.1 - Configuration
Disable the linkify option in MarkdownIt configuration to avoid the affected quadratic linkification paths.
markdown-it linkify = false
Event History
Frequently Asked Questions
What inputs can trigger the excessive processing time?
Schema-less email-like text split across many soft-broken lines can trigger repeated rebuilding of inline children. Repeated unregistered scheme prefixes such as "a://" can also trigger repeated rescanning; ordinary "http://" links are consumed earlier and remain linear.
Is this reachable with the default parser settings?
No. The affected paths are specifically in handling enabled by the linkify: true option, so inputs are exposed when markdown-it is configured with linkification enabled.
What would an attacker need to do to exploit this?
An attacker needs to cause the application to render a crafted Markdown payload while linkify is enabled. The impact is increased CPU time during rendering, with measured processing growing roughly fourfold when the supplied payload size doubles.
How can I identify potentially affected usage?
Review MarkdownIt initialization for linkify: true and identify whether untrusted or large user-controlled Markdown is rendered through those instances. Test with repeated soft-broken schema-less email text and repeated unregistered "<text>://" sequences rather than http:// links.