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

Denial of Service in GitLab CE/EE Grape API JSON parsing middleware

IdentifiersCVE-2026-7250CWE-20

CVE-2026-7250 is a denial-of-service vulnerability in GitLab Community Edition and Enterprise Edition caused by improper input validation in the API request parsing middleware, specifically the Grape API JSON parsing middleware. GitLab states that under certain conditions, malformed or specially crafted API input can be processed in a way that allows an unauthenticated attacker to trigger a service disruption. The issue affects GitLab CE/EE all versions from 12.10 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2.

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 unauthenticated remote attacker to cause a denial-of-service condition, degrading or interrupting availability of affected GitLab services that rely on the vulnerable API request parsing path. No evidence is provided in the supplied content of code execution, privilege escalation, or data exposure from this issue; the documented impact is service availability disruption.

Mitigation

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

If immediate patching is not possible, reduce exposure of GitLab API endpoints to untrusted networks, apply upstream rate limiting and request filtering for malformed or abusive JSON API traffic, and monitor for spikes in API parsing failures or service instability. These are general mitigations inferred from the attack surface; the provided content does not specify an official vendor workaround beyond upgrading.

Remediation

Patch, then assume compromise.

Upgrade affected self-managed GitLab CE/EE installations to a fixed version: 18.10.8, 18.11.5, 19.0.2, or a later release in the respective supported branch. GitLab.com is already patched according to the provided content, and GitLab Dedicated customers do not need to take action.
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.