High

Unauthenticated DoS in GitLab CI/CD job update API

IdentifiersCVE-2026-1659CWE-20

CVE-2026-1659 is a denial-of-service vulnerability in GitLab CE/EE caused by insufficient input validation in the CI/CD job update API. According to the provided content, the issue affects all versions from 9.0 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3. An unauthenticated attacker can send specially crafted requests or payloads to the affected API endpoint and trigger resource exhaustion or service instability, resulting in disruption of GitLab CI/CD-related operations.

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.

Start free trial

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 denial of service against affected GitLab instances. The provided context indicates this can overwhelm the system and disrupt CI/CD pipelines, code deployment, and related workflow operations. No evidence was provided that this vulnerability enables code execution, authentication bypass beyond anonymous access to the vulnerable endpoint, or data exfiltration.

Mitigation

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

If immediate patching is not possible, reduce exposure to the CI/CD job update API by restricting network access to trusted sources, placing the instance behind filtering or rate-limiting controls, and monitoring for bursts of malformed or specially crafted requests targeting CI/CD-related endpoints. Because the issue is unauthenticated, minimizing public reachability of the affected API surface is the most relevant temporary mitigation. Specific vendor-endorsed workaround details were not provided in the content.

Remediation

Patch, then assume compromise.

Upgrade self-managed GitLab CE/EE instances to a fixed release: 18.9.7, 18.10.6, 18.11.3, or later, as applicable to the deployed release train. The provided content states GitLab released emergency security updates on 2026-05-13 and that cloud-hosted GitLab platforms were already patched. For single-node deployments, plan for downtime because database migrations must complete before restart; multi-node deployments can use standard zero-downtime upgrade procedures.

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

GitLabGitlab Ceapplication

GitLabGitlab Eeapplication

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

ACTIVITY FEED

Recent activity

4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

4 SOURCESView more in app

cyber security newsNews

May 14, 2026

Critical GitLab Vulnerabilities Enables XSS and Unauthenticated DoS Attacks

A high-severity unauthenticated denial-of-service vulnerability in the GitLab CI/CD job update API that can be exploited with crafted payloads to overwhelm the system.

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.

Start free trial

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 activity3