Loading vulnerability…
CVE-2025-1257 is a medium-severity denial-of-service vulnerability in GitLab Enterprise Edition affecting the Approval Rules functionality. The issue affects GitLab EE versions starting with 12.3 before 17.7.7, 17.8 before 17.8.5, and 17.9 before 17.9.2. The flaw is described as arising from an unbounded field in Approval Rules processing, allowing an attacker to manipulate specific API inputs in a way that can exhaust resources or otherwise destabilize the application, resulting in a denial-of-service condition.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A medium-severity GitLab-related vulnerability mentioned as one of several additional flaws that may enable remote code execution, denial of service, privilege escalation, or unauthorized access to sensitive data.
A denial-of-service vulnerability in GitLab EE approval rules caused by an unbounded field, allowing an attacker to trigger DoS via specific API inputs.
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.