Security readout for executives and security teams
Plain-English summary
GitLab disclosed a denial-of-service flaw in GitLab CE/EE. An authenticated user could abuse a Bitbucket Server import endpoint by repeatedly causing large responses, exhausting resources and disrupting availability. This is not described as data theft or code execution, but it can affect service uptime.
Executive priority
Treat as a timely availability risk, especially for business-critical GitLab instances. Schedule prompt patching, but this is not currently supported by sources as an active exploitation emergency or data breach issue.
Technical view
CVE-2026-2845 is CWE-770: allocation of resources without limits or throttling. It affects GitLab CE/EE from 11.2 before 18.7.5, 18.8 before 18.8.5, and 18.9 before 18.9.1. CVSS is 6.5: network reachable, low complexity, low privileges, no user interaction, high availability impact.
Likely exposure
Organizations running self-managed GitLab CE/EE in the affected version ranges are exposed if authenticated users can reach the Bitbucket Server import functionality. GitLab.com exposure is not stated in the provided sources.
Exploitation context
The CVE is not listed as KEV, and the provided sources do not state active exploitation. Exploitation requires an authenticated GitLab user and targets availability through repeated large import-related responses, not confidentiality or integrity.
Researcher notes
Key boundaries are authenticated access and the Bitbucket Server import endpoint. Public details are limited; avoid assuming unauthenticated exploitation, data impact, or exploit availability. Validate exposure by version and feature accessibility rather than scanner claims alone.
Mitigation direction
- Upgrade GitLab to 18.7.5, 18.8.5, 18.9.1, or later supported fixed versions.
- Prioritize internet-facing or broadly accessible self-managed GitLab instances.
- If immediate upgrade is not possible, check GitLab guidance for supported temporary controls.
- Review whether Bitbucket Server import access is necessary for current users.
Validation and detection
- Inventory all self-managed GitLab CE/EE versions.
- Confirm affected instances are below 18.7.5, 18.8.5, or 18.9.1.
- Verify upgraded instances report a fixed GitLab version.
- Review logs for repeated Bitbucket Server import activity and resource exhaustion symptoms.
- Confirm only appropriate authenticated users can access import features.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-2845 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.