CVE-2026-48988: markdown-it: Quadratic complexity DoS in smartquotes rule via replaceAt string operations

Published Jun 15, 2026
·
Updated

Summary

A quadratic time complexity vulnerability exists in markdown-it's smartquotes rule (enabled via the typographer: true option). An attacker can craft a markdown input consisting of consecutive quotation marks that causes the parser to consume excessive CPU time, leading to denial of service.

Details

The vulnerability is in the replaceAt() helper function used by the smartquotes rule in lib/rulescore/smartquotes.mjs:

javascript function replaceAt (str, index, ch) { return str.slice(0, index) + ch + str.slice(index + 1) }

When markdown-it processes a text token containing many quotation marks (either " or ') with typographer: true, the smartquotes rule iterates through each quote character and calls replaceAt() to substitute it with a typographic (curly) quote. Each call to replaceAt() creates three new string slices and concatenates them, which is an O(n) operation where n is the length of the string.

Since this is called once per quote character in the token, and there are n quote characters, the total time complexity becomes O(n^2).

The root cause is that the smartquotes rule modifies token.content in place using string slicing rather than building the result incrementally. The processinlines() function (line 14) processes each quote in the text token, and for matching quote pairs, calls replaceAt() on both the opening and closing token's content (lines 151-152). When the entire input is a single text token of quote characters, this results in quadratic behavior.

PoC

javascript const md = require('markdown-it'); const instance = md({ typographer: true });

// 160,000 consecutive double-quote characters const payload = '"'.repeat(160000);

console.time('render'); instance.render(payload); console.timeEnd('render'); // Output: render: ~21000ms (21 seconds)

// Compare with typographer disabled: const safe = md({ typographer: false }); console.time('render-safe'); safe.render(payload); console.timeEnd('render-safe'); // Output: render-safe: ~8ms

Measured timing on a modern system: - 10,000 quotes: ~19ms - 20,000 quotes: ~51ms - 40,000 quotes: ~212ms - 80,000 quotes: ~5,430ms - 160,000 quotes: ~21,198ms

The scaling is clearly superlinear (quadratic), with the 80K->160K step showing a ~3.9x increase for a 2x input increase, consistent with O(n^2).

Impact

Applications that render user-supplied markdown with typographer: true are vulnerable to denial of service. An attacker can submit a relatively small payload (160KB of quote characters) that causes the server to spend over 21 seconds processing a single request. Repeated submissions can exhaust server CPU resources and prevent legitimate users from being served.

The impact is mitigated by the fact that the typographer option defaults to false and must be explicitly enabled. However, the typographer feature is commonly enabled in production applications that want smart typography, and the markdown-it documentation prominently suggests enabling it.

A suggested fix would be to replace the replaceAt() approach with an array-based or StringBuilder-style approach that collects all replacements and applies them in a single pass, reducing the time complexity to O(n).

Other sources

markdown-it is a Markdown parser. Versions 14.1.1 and below contain a denial-of-service vulnerability when typographer: true is enabled, due to quadratic (O(n^2)) processing in the smartquotes rule. The issue stems from repeatedly modifying strings with replaceAt(), which performs O(n) slicing and concatenation per quote character. This can cause excessive CPU consumption when parsing quote-heavy, user-supplied markdown and may let attackers degrade or disrupt service availability. Although typographer is disabled by default, many production apps enable it for smart typography, making the issue relevant. This issue has been fixed in version 14.2.0.

MITRE

Affected Software

2 affected componentsFixes available
npm/markdown-it<=14.1.1
14.2.0
Markdown-it Project Markdown-it<14.2.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/markdown-it to a version that resolves this vulnerability.

    Fixed in 14.2.0
  2. Configuration

    Disable the typographer option by setting typographer: false when rendering untrusted or user-supplied markdown to avoid the smartquotes rule and its quadratic behavior.

    markdown-it typographer = false

Event History

Jun 15, 2026
Advisory Published
via GitHub·08:41 PM
Data Sourced
via GitHub·08:41 PM
DescriptionSeverityWeaknessAffected Software
Jun 17, 2026
CVE Published
via MITRE·08:54 PM
Data Sourced
via MITRE·08:54 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-48988?

CVE-2026-48988 has a medium severity score of 5.3.

2

How does CVE-2026-48988 affect markdown-it functionality?

CVE-2026-48988 affects markdown-it by introducing a quadratic time complexity vulnerability that can lead to denial of service.

3

Who is affected by CVE-2026-48988?

Users who enable the 'typographer: true' option in markdown-it are particularly vulnerable to CVE-2026-48988.

4

How do I fix CVE-2026-48988?

To mitigate CVE-2026-48988, disable the 'typographer' option or update to a patched version of markdown-it.

5

What kind of attack can occur due to CVE-2026-48988?

An attacker can exploit CVE-2026-48988 by crafting input with consecutive quotation marks, causing excessive CPU usage.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203