Packages / markdown-it / Security

ModerateVulnerabilityGHSA-253c-mchw-3w2rPublished 29 Sep 2026

markdown-it linkify: true has two quadratic paths, so a few hundred KB of markdown blocks the event loop for tens of seconds

Your version

Affected releases · markdown-it

  • 15.x15.0.0Fixed in 15.0.1
  • 14.x14.0.0 – 14.3.0Fixed in 14.3.1
  • 13.x and older2.0.0 – 13.0.2No fix, no longer updated

On 15.x, the newest line:

npm install markdown-it@15.0.1
Every release on a timeline
15.x
  1. Affected

    15.0.0

    1 release

  2. Fixed

    15.0.1 – 15.0.3

    3 releases, latest

14.x
  1. Affected

    14.0.0 – 14.3.0

    5 releases

  2. Fixed

    14.3.1 – 14.3.3

    3 releases

13.x
  1. Affected

    13.0.0 – 13.0.2

    3 releases

12.x
  1. Affected

    12.0.0 – 12.3.2

    12 releases

11.x
  1. Affected

    11.0.0 – 11.0.1

    2 releases

10.x
  1. Affected

    10.0.0

    1 release

9.x
  1. Affected

    9.0.0 – 9.1.0

    3 releases

8.x
  1. Affected

    8.0.0 – 8.4.2

    12 releases

7.x
  1. Affected

    7.0.0 – 7.0.1

    2 releases

6.x
  1. Affected

    6.0.0 – 6.1.1

    8 releases

5.x
  1. Affected

    5.0.0 – 5.1.0

    5 releases

4.x
  1. Affected

    4.0.0 – 4.4.0

    13 releases

3.x
  1. Affected

    3.0.0 – 3.1.0

    9 releases

2.x
  1. Affected

    2.0.0 – 2.2.1

    7 releases

89 stable releases of markdown-it, oldest to newest, one row per major.

What happens

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/rules_core/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/rules_inline/linkify.ts runs state.pending.match(SCHEME_RE) 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.

N5,00010,00020,00040,000
'a@b.co\n'.repeat(N), 34KB to 273KB1.1s4.7s19.6s89s
'a://'.repeat(N), 20KB to 156KB0.25s0.76s3.1s15.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 SCHEME_RE 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.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.