Loading vulnerability…
CVE-2025-14869 is an unauthenticated denial-of-service vulnerability in GitLab Community Edition and Enterprise Edition affecting all versions from 18.5 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3. The flaw is in GitLab's API layer and is caused by improper validation of specified input quantities on certain API endpoints. A remote attacker can send specially crafted payloads that trigger disproportionate resource consumption during request processing, leading to exhaustion of CPU, memory, or related system resources and impairing service availability.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity unauthenticated denial-of-service vulnerability in GitLab internal API endpoints.
An unauthenticated denial-of-service vulnerability in GitLab's API layer caused by improper validation of specified quantity in input, allowing remote attackers to exhaust system resources and disrupt availability.
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.