CVE-2025-10497 is a denial-of-service vulnerability in the event collection subsystem of GitLab Community Edition and Enterprise Edition. Affected versions are 17.10 before 18.3.5, 18.4 before 18.4.3, and 18.5 before 18.5.1. The flaw is caused by insufficient validation and resource-control handling for incoming event collection payloads, allowing specially crafted requests to trigger excessive resource allocation and processing. A remote unauthenticated attacker can exploit the issue by sending crafted payloads to the exposed event collection functionality, potentially exhausting CPU, memory, or related resources and rendering the GitLab instance unavailable.
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 denial-of-service vulnerability in GitLab event collection where unauthenticated users could send crafted payloads to disrupt service.
A vulnerability listed as trending; no technical details provided in the content.
A denial of service vulnerability in GitLab Community Edition and Enterprise Edition event collection subsystem that allows unauthenticated remote attackers to trigger excessive resource allocation and cause service unavailability.
A previously addressed GitLab vulnerability affecting event collection; no further technical details are provided in the content.
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.