dbcve.org
GitLabApplication

CVE-2026-2845

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-25
Fix available
A fix is available. Upgrade to 18.7.5 / 18.8.5 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
An issue has been discovered in GitLab CE/EE affecting all versions from 11.2 before 18.7.5, 18.8 before 18.8.5, and 18.9 before 18.9.1 that could have allowed an authenticated user to cause denial of service by exploiting a Bitbucket Server import endpoint via repeatedly sending large responses.

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 · moderate confidence

An authenticated user can cause denial of service by exploiting the Bitbucket Server import endpoint in GitLab CE/EE, repeatedly sending large responses that exhaust server resources. This affects versions 11.2 through 18.7.4, 18.8.0 through 18.8.4, and 18.9.0.

MitigationUpgrade GitLab to version 18.7.5, 18.8.5, 18.9.1 or later. If immediate upgrade is not possible, consider rate limiting or temporarily disabling the Bitbucket Server import functionality at the load balancer/proxy level.

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:>= 11.2.0, < 18.7.5>= 18.8.0, < 18.8.5= 18.9.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. Check GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or access the Admin Area > Settings > General page to view the installed GitLab version
    Affected if The version falls within 11.2.0 to 18.7.4, 18.8.0 to 18.8.4, or equals 18.9.0
  2. Verify Bitbucket Server import is enabled
    Navigate to Admin Area > Settings > Visibility and access controls > Import sources, or use the API endpoint `/api/v4/application/settings` to check the `bitbucket_server_import_enabled` setting
    Affected if The Bitbucket Server import source is enabled in the GitLab settings
  3. Confirm authenticated users can access import functionality
    Check if the project import feature is available to regular users (not just admins). Verify in Admin Area > Settings > Visibility and access controls that the 'Import sources' allows authenticated users to import projects
    Affected if Authenticated (non-admin) users have access to the project import feature including Bitbucket Server imports
  4. Review access logs for import endpoint activity
    Check GitLab production logs or load balancer/access logs for repeated requests to `/import/bitbucket_server` endpoints from authenticated users
    Affected if Repeated requests to the Bitbucket Server import endpoint are observed, which may indicate active exploitation

A GitLab instance is affected if it runs a version between 11.2.0 and 18.7.4, between 18.8.0 and 18.8.4, or exactly 18.9.0, AND has the Bitbucket Server import feature enabled for 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.7.5 / 18.8.5 or later
Fixed in 18.7.518.8.5
Interim mitigation

Upgrade GitLab to version 18.7.5, 18.8.5, 18.9.1 or later. If immediate upgrade is not possible, consider rate limiting or temporarily disabling the Bitbucket Server import functionality at the load balancer/proxy level.

Recommended fix High confidence

GitLab 18.9.1 (or 18.7.5/18.8.5 depending on your release branch)

  1. Review the GitLab upgrade documentation for your current version at https://docs.gitlab.com/ee/update/
  2. Ensure you have a complete backup of your GitLab instance including database and repositories
  3. Stop GitLab services before upgrading
  4. Upgrade to GitLab 18.9.1 (or at minimum 18.7.5 or 18.8.5 depending on your branch) using your package manager or source method
  5. Verify the upgrade completed successfully by checking the GitLab version in the Admin Area
  6. Restart GitLab services
Caveat Review GitLab release notes for your target version for any breaking changes or required migration steps

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2845 — 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-2845 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