CommonMark has DisallowedRawHtml extension bypass via whitespace in HTML tag names
Published 6 Mar 2026 · Updated 20 Mar 2026
Affected package
- Affected
- >=2.0.0 <2.8.1
- Fixed in
- 2.8.1
composer require league/commonmark:^2.8.1Details
Impact
The DisallowedRawHtml extension can be bypassed by inserting a newline, tab, or other ASCII whitespace character between a disallowed HTML tag name and the closing >. For example, <script\n> would pass through unfiltered and be rendered as a valid HTML tag by browsers. This is a cross-site scripting (XSS) vector for any application that relies on this extension to sanitize untrusted user input.
All applications using the DisallowedRawHtml extension to process untrusted markdown are affected. Applications that use a dedicated HTML sanitizer (such as HTML Purifier) on the rendered output are not affected.
Patches
Fixed in 2.8.1. The regex character class [ \/>] was changed to [\s\/>] to match all whitespace characters that browsers accept as valid tag name terminators.
Workarounds
- Set the
html_inputconfiguration option to'escape'or'strip'to disable all raw HTML, though this is a broader restriction than theDisallowedRawHtmlextension provides. - Pass the rendered HTML through a dedicated HTML sanitizer before serving it to users (always recommended)
Is GHSA-4v6x-c7xx-hw9f in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected league/commonmark, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.