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 issue import

IdentifiersCVE-2026-1660CWE-20

CVE-2026-1660 is a denial-of-service vulnerability in GitLab Community Edition (CE) and Enterprise Edition (EE). According to the provided advisory text, the issue affects all versions from 12.3 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1. Under certain conditions, an authenticated user could trigger denial of service during issue import because of improper input validation. No additional technical detail about the specific vulnerable function or code path was provided in the supplied content.

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 cause denial of service in GitLab during issue import operations. The supplied content does not specify whether the impact is limited to a single import job, a project-scoped service disruption, or broader instance instability, so the precise operational scope is currently not available.

Mitigation

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

If immediate patching is not possible, reduce exposure by restricting which authenticated users can perform issue imports, closely monitoring import activity for malformed or abusive input, and applying operational safeguards such as rate limiting or temporary disabling of issue import functionality where feasible. Specific vendor-recommended mitigations were not provided in the supplied content.

Remediation

Patch, then assume compromise.

Upgrade GitLab CE/EE to a fixed release. The provided content identifies the remediated versions as 18.9.6 or later in the 18.9 series, 18.10.4 or later in the 18.10 series, and 18.11.1 or later in the 18.11 series. Versions from 12.3 up to but excluding those fixed releases are affected.
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.