GitLab CE/EE Markdown Preview CPU Exhaustion DoS
GitLab Community Edition (CE) and Enterprise Edition (EE) contain a denial-of-service vulnerability in markdown preview processing. According to the provided content, an unauthenticated attacker can submit specially crafted markdown files that trigger exponential processing during markdown preview, resulting in excessive CPU consumption. The issue affects GitLab CE/EE all versions from 18.7 before 18.7.4 and 18.8 before 18.8.4.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
GitLab denial-of-service vulnerability causing CPU exhaustion via specially crafted Markdown that triggers exponential processing loops.
Unauthenticated CPU-exhaustion DoS via specially crafted Markdown causing exponential processing in Markdown Preview.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.