dbcve.org
GitLabApplication

CVE-2026-1660

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-22
Fix available
A fix is available. Upgrade to 18.9.6 / 18.10.4 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.3 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that under certain conditions could have allowed an authenticated user to cause denial of service when importing issues due to improper input validation.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

GitLab CE/EE versions 12.3 through 18.11.x contained an input validation flaw in the issue import feature that allowed authenticated users to trigger denial of service conditions via specially crafted import requests.

MitigationUpgrade GitLab to version 18.9.6, 18.10.4, 18.11.1 or later to receive the patched input validation logic.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GitLabApplication
Affected:>= 12.3.0, < 18.9.6>= 18.10.0, < 18.10.4= 18.11.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed GitLab version
    Navigate to Admin Area > Settings > General, or check the /help page, or run `gitlab-rake gitlab:env:info` to display version information
    Affected if The version falls within >= 12.3.0 and < 18.9.6, OR >= 18.10.0 and < 18.10.4, OR equals 18.11.0
  2. Verify the issue import feature is enabled
    Go to Admin Area > Settings > Issue Tracking > scroll to Import issues section, or check the project settings for issue import options
    Affected if Issue import is enabled and accessible to authenticated users on at least one project
  3. Confirm authenticated user access exists
    Review user accounts in Admin Area > Users, or check if external or internal authentication is configured allowing user registration or LDAP/sAML integration
    Affected if The instance has at least one authenticated user account that can access the issue import feature

The environment is affected if the installed GitLab version matches the vulnerable ranges AND the issue import feature is accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 18.9.6 / 18.10.4 or later
Fixed in 18.9.618.10.4
Interim mitigation

Upgrade GitLab to version 18.9.6, 18.10.4, 18.11.1 or later to receive the patched input validation logic.

Recommended fix High confidence

18.11.1 or later (18.10.4+ for 18.10.x branch, 18.9.6+ for 18.9.x branch)

  1. 1. Back up your GitLab instance data before proceeding with the upgrade
  2. 2. Plan your upgrade path based on your current version - aim for the latest stable release in your major version branch
  3. 3. For GitLab installations using Omnibus: run 'sudo gitlab-ctl stop' to stop services before upgrade
  4. 4. For package-based installations: download and install the appropriate GitLab package for your target version
  5. 5. For source installations: update source code to the fixed version tag (e.g., v18.11.1 for 18.11.x branch)
  6. 6. Run 'sudo gitlab-ctl reconfigure' after package installation to apply configuration
  7. 7. Verify GitLab services are running with 'sudo gitlab-ctl status'
  8. 8. Test issue import functionality to confirm the fix is working
Caveat Upgrading across multiple minor versions may require reading the upgrade documentation for intermediate breaking changes; ensure you review the changelog for your upgrade path

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1660 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1660 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data