Loading vulnerability…
CVE-2026-15975 is a denial-of-service vulnerability in GitLab Community Edition and Enterprise Edition affecting all versions from 11.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1. The flaw is caused by insufficient resource throttling during processing of merge request discussions. Under certain conditions, an unauthenticated attacker can send crafted requests to the merge request discussion functionality and trigger excessive resource consumption, leading to instability or service interruption on self-managed GitLab instances.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity denial-of-service vulnerability in self-managed GitLab CE/EE that allows unauthenticated attackers to crash or severely degrade instances via crafted requests to the merge request discussion endpoint.
A high-severity denial-of-service vulnerability in GitLab merge request discussions caused by insufficient resource throttling, allowing unauthenticated attackers to disrupt server availability.
A denial-of-service vulnerability in GitLab Merge Request Discussions that could allow an unauthenticated user to cause service disruption because of insufficient resource throttling.
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.