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

Denial of Service in GitLab CE/EE Group Placeholder Reassignments API file upload handling

IdentifiersCVE-2026-1500CWE-400

CVE-2026-1500 is a medium-severity denial-of-service vulnerability in GitLab Community Edition and Enterprise Edition affecting all versions from 17.10 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2. According to the provided content, the issue affects the Group Placeholder Reassignments API and can be triggered when GitLab processes a specially crafted file upload. Under certain conditions, an authenticated user can cause uncontrolled resource consumption during file processing, resulting in service degradation or denial of service. The available information does not identify the exact vulnerable function or code path beyond the API/file-upload processing context.

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 allows an authenticated attacker to consume excessive server resources and cause denial of service in the affected GitLab instance. The practical impact is disruption of availability for GitLab services or affected API functionality, potentially degrading responsiveness or making the application unavailable to legitimate users while the crafted upload is processed.

Mitigation

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

If immediate patching is not possible, reduce exposure of the vulnerable upload path by restricting access to authenticated users who require the Group Placeholder Reassignments API, applying tighter upload controls and monitoring for anomalous resource consumption associated with file uploads. Operational mitigations may lessen exploitability, but the provided content does not describe an official vendor workaround; upgrading is the primary mitigation.

Remediation

Patch, then assume compromise.

Upgrade affected GitLab CE/EE installations to a fixed release. The provided content states that GitLab remediated the issue in versions 18.10.8, 18.11.5, and 19.0.2. Self-managed deployments running affected versions should upgrade to the appropriate patched version or later.
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.

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 activity2

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