Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
MediumPublic exploit

Denial of Service in GitLab CE/EE discussions endpoint

IdentifiersCVE-2025-0186CWE-400

CVE-2025-0186 is a denial-of-service vulnerability in GitLab Community Edition (CE) and Enterprise Edition (EE). It affects all versions from 10.6 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1. According to the provided content, an authenticated user could trigger excessive server resource consumption by sending crafted requests to a discussions endpoint, resulting in denial of service under certain conditions. Specific vulnerable functions or internal code paths are not provided in the available information.

Share:
For your environment

Are you exposed to this one?

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.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can exhaust server resources and degrade or disrupt GitLab service availability. This can prevent legitimate users from accessing affected functionality and may impact overall platform responsiveness or stability. Based on the available information, the impact is limited to denial of service; no evidence is provided for code execution, privilege escalation, or data exposure.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure of the affected discussions endpoint to untrusted authenticated users where feasible, and apply rate limiting, request throttling, and resource monitoring to detect and suppress abusive crafted requests. Operational mitigations may lessen impact but do not replace upgrading to a fixed release.

Remediation

Patch, then assume compromise.

Upgrade GitLab CE/EE to a fixed version: 18.9.6 or later in the 18.9 series, 18.10.4 or later in the 18.10 series, or 18.11.1 or later in the 18.11 series. Any affected version from 10.6 up to, but not including, those releases should be considered vulnerable.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GitLabGitlabapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1

Community discussion across Reddit, Mastodon, and other social sources.