Security readout for executives and security teams
Plain-English summary
CVE-2026-1662 is a GitLab denial-of-service flaw. An unauthenticated attacker could send specially crafted requests to the Jira events endpoint and consume resources, potentially disrupting GitLab availability. It affects GitLab CE/EE versions from 14.4 before the fixed 18.7.5, 18.8.5, and 18.9.1 releases.
Executive priority
Treat as a high-priority availability risk for self-managed GitLab. It does not indicate data theft or code execution, but disruption to GitLab can affect software delivery, incident response, and developer productivity. Patch exposed or business-critical instances first.
Technical view
The issue is CWE-770: allocation of resources without limits or throttling. CVSS 3.1 is 7.5, network exploitable, low complexity, no privileges, no user interaction, with high availability impact only. GitLab states it remediated the issue in 18.7.5, 18.8.5, and 18.9.1.
Likely exposure
Self-managed GitLab CE/EE instances in the affected version ranges are the relevant exposure. Internet-facing GitLab instances or instances with externally reachable Jira event handling are more concerning. The sources do not identify GitLab.com exposure status or any affected non-GitLab products.
Exploitation context
The CVE states exploitation can be unauthenticated via specially crafted requests. The bundled KEV flag is false, and no provided public source confirms active exploitation in the wild. HackerOne and GitLab issue references are listed but marked permissions-required, limiting public technical detail.
Researcher notes
Public technical detail is limited because the GitLab issue and HackerOne report are marked permissions-required. Analysis should focus on version exposure, endpoint reachability, and availability telemetry. Avoid assuming exploit details beyond the CVE description and GitLab release statement.
Mitigation direction
- Upgrade GitLab CE/EE to 18.7.5, 18.8.5, 18.9.1, or a later fixed release.
- Prioritize externally reachable GitLab instances and those using Jira event integrations.
- Review GitLab’s patch release advisory for any deployment-specific instructions.
- If immediate upgrade is delayed, check vendor guidance for supported temporary mitigations.
Validation and detection
- Inventory all self-managed GitLab CE/EE versions.
- Flag versions from 14.4 before 18.7.5, 18.8 before 18.8.5, and 18.9 before 18.9.1.
- Confirm whether the Jira events endpoint is reachable from untrusted networks.
- Review monitoring for unusual request volume or availability degradation around Jira event handling.
- Verify upgraded instances report a fixed GitLab version.
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-1662 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
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/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:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- GitLab Issue #588206CVE reference · issue-tracking, permissions-required
- HackerOne Bug Bounty Report #3519694CVE reference · technical-description, exploit
- https://about.gitlab.com/releases/2026/02/25/patch-release-gitlab-18-9-1-released/CVE reference
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.