Loading vulnerability…
CVE-2026-0958 is a denial-of-service vulnerability in GitLab Community Edition and Enterprise Edition caused by the ability to bypass limits enforced by the JSON validation middleware. A remote, unauthenticated attacker can submit crafted requests that evade intended validation constraints and drive excessive memory consumption or CPU utilization. The issue affects GitLab CE/EE versions from 18.4 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4.
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.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity GitLab vulnerability enabling denial of service (DoS) via resource exhaustion.
A high-severity denial-of-service/resource exhaustion issue in GitLab’s JSON validation middleware that can be abused to consume CPU/memory.
GitLab denial-of-service vulnerability enabling memory/CPU exhaustion by bypassing JSON validation middleware limits.
Unauthenticated DoS via bypass of JSON validation middleware limits leading to CPU/memory 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.