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

Denial of Service in GitLab EE GraphQL SBOM API

IdentifiersCVE-2026-1101CWE-20

CVE-2026-1101 is a denial-of-service vulnerability in GitLab Enterprise Edition (EE) affecting all versions from 18.2 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3. The issue is in the GraphQL SBOM API, where improper input validation in GraphQL queries allows an authenticated user to submit crafted requests that can exhaust resources or otherwise destabilize processing, resulting in denial of service of the GitLab instance.

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 can cause denial of service affecting the GitLab instance, disrupting availability for users and preventing normal operation of the platform. The provided context indicates the impact can extend beyond a single request path to the overall instance.

Mitigation

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

If immediate patching is not possible, reduce exposure of the vulnerable GraphQL SBOM API to untrusted authenticated users, apply restrictive access controls to accounts that can reach the affected functionality, and monitor/rate-limit abusive GraphQL query patterns where operationally feasible. However, no complete mitigation is provided in the source context; upgrading is the authoritative fix.

Remediation

Patch, then assume compromise.

Upgrade GitLab EE to a fixed version: 18.8.9, 18.9.5, 18.10.3, or later in the respective release trains. GitLab urged self-managed customers to upgrade immediately. GitLab.com was already patched, and GitLab Dedicated customers did not need to take action according to the provided context.
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 activity1

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