Loading vulnerability…
A denial-of-service vulnerability in the GitLab Commit API affects GitLab Community Edition and Enterprise Edition. An authenticated user can trigger the flaw by sending crafted API requests containing excessively large content parameters, causing resource exhaustion and degrading or interrupting service availability. The issue affects GitLab CE/EE versions from 6.3 before 18.4.6, 18.5 before 18.5.4, and 18.6 before 18.6.2.
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.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A medium-severity denial-of-service vulnerability in GitLab (specific affected component not detailed beyond being part of the DoS set).
A medium-severity denial-of-service vulnerability in the GitLab Commit API that could allow an authenticated user to disrupt service using crafted API calls with large content parameters.
A denial-of-service vulnerability in GitLab's Commit API where crafted requests with large content parameters can cause resource exhaustion.
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.