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 GraphQL API

IdentifiersCVE-2025-3922CWE-770· Allocation of Resources Without…

CVE-2025-3922 is a denial-of-service vulnerability in GitLab Community Edition (CE) and Enterprise Edition (EE) caused by insufficient resource allocation limits in the GraphQL API. According to the provided information, the issue affects all versions from 12.4 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1. Under certain conditions, an authenticated user could send GraphQL requests that overwhelm system resources, resulting in service degradation or outage.

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.

A successful exploit allows an authenticated user to consume excessive server resources through the GitLab GraphQL API, potentially causing denial of service. The likely impact is degradation or interruption of GitLab availability for legitimate users, including possible slowdown, instability, or temporary unavailability of affected services depending on deployment size and resource constraints.

Mitigation

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

If immediate patching is not possible, reduce exposure to the GraphQL API where operationally feasible, restrict access to trusted authenticated users only, and apply rate limiting, request throttling, and resource monitoring around GitLab application traffic to reduce the likelihood and impact of resource-exhaustion attempts. Because exploitation requires authentication, tightening account provisioning and monitoring for abusive GraphQL usage may also help limit risk until upgrades can be applied.

Remediation

Patch, then assume compromise.

Upgrade GitLab CE/EE to a fixed release: 18.9.6 or later, 18.10.4 or later, or 18.11.1 or later, depending on the supported upgrade path in use. These versions remediate the insufficient resource allocation limits in the GraphQL API.
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.