Multiple issues in the parsing process can lead to a denial of service. An unauthenticated attacker can submit specially crafted Markdown to consume disproportionate CPU time, potentially occupying all available PHP workers and preventing legitimate requests from completing. The issues occur across three independent parsing paths:
1. Fenced code block detection: The `FencedCodeStartParser` uses a non-atomic lookahead that performs quadratic work when processing long backtick runs.
2. Reference link label lookup: The `CloseBracketParser::tryParseReference()` function and `ReferenceMap::get()` method perform excessive normalization (including `trim`, `preg replace`, `mb check encoding`, and `strtolower`) on labels. Nested brackets can trigger multiple lookups, resulting in effectively quadratic work.
3. Delimiter processing: The `DelimiterStack::processDelimiters()` function, along with `EmphasisDelimiterProcessor::getCacheKey()`, `StrikethroughDelimiterProcessor`, and `MarkDelimiterProcessor`, uses unbounded cache keys based on delimiter run lengths. This forces full backward re-scans of openers, resulting in super-linear work (approximately n^1.5).