CVE-2026-1662
Denial of Service in GitLab Jira Events Endpoint
Publication date: 2026-02-25
Last updated on: 2026-02-28
Assigner: GitLab Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gitlab | gitlab | From 18.8.0 (inc) to 18.8.5 (exc) |
| gitlab | gitlab | From 18.8.0 (inc) to 18.8.5 (exc) |
| gitlab | gitlab | 18.9.0 |
| gitlab | gitlab | 18.9.0 |
| gitlab | gitlab | From 14.4.0 (inc) to 18.7.5 (exc) |
| gitlab | gitlab | From 14.4.0 (inc) to 18.7.5 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-770 | The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability affects GitLab CE/EE versions from 14.4 before 18.7.5, 18.8 before 18.8.5, and 18.9 before 18.9.1. It allows an unauthenticated user to cause a Denial of Service (DoS) by sending specially crafted requests to the Jira events endpoint.
How can this vulnerability impact me? :
The impact of this vulnerability is a Denial of Service condition, meaning that an attacker can disrupt the normal operation of the GitLab service by making it unavailable or unresponsive through specially crafted requests to the Jira events endpoint.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade GitLab CE/EE to a fixed version. The affected versions are all releases from 14.4 before 18.7.5, 18.8 before 18.8.5, and 18.9 before 18.9.1. Applying the latest patches or upgrading to versions 18.7.5, 18.8.5, 18.9.1 or later will remediate the issue.