Bug 2526262 - CVE-2026-48988 libgit2: markdown-it: Denial of Service via quadratic processing of smartquotes with typographer enabled [fedora-all]
Summary: CVE-2026-48988 libgit2: markdown-it: Denial of Service via quadratic processi...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: libgit2
Version: rawhide
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Fabio Valentini
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["71f48a1b-0719-4fd8-ad05-4...
Depends On:
Blocks: CVE-2026-48988
TreeView+ depends on / blocked
 
Reported: 2026-08-31 11:18 UTC by Marian Rehak
Modified: 2026-09-01 15:47 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-09-01 15:47:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Marian Rehak 2026-08-31 11:18:09 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

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.

Comment 1 Fabio Valentini 2026-09-01 15:47:48 UTC
markdown-it is only referenced in the JavaScript tooling that's used to build the API docs, which isn't done for the Fedora packages - and even if it were, it would only be used to parse "trusted" input.


Note You need to log in before you can comment on or make changes to this bug.