CVE-2026-2619
Authorization Bypass in GitLab EE Allows Vulnerability Flag Modification
Publication date: 2026-04-08
Last updated on: 2026-04-14
Assigner: GitLab Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gitlab | gitlab | From 18.9.0 (inc) to 18.9.5 (exc) |
| gitlab | gitlab | From 18.10.0 (inc) to 18.10.3 (exc) |
| gitlab | gitlab | From 18.6.0 (inc) to 18.8.9 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-863 | The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in GitLab EE affects certain versions before specific patch releases. It allows an authenticated user with auditor privileges to modify vulnerability flag data in private projects due to incorrect authorization checks.
How can this vulnerability impact me? :
The vulnerability could allow an auditor-level user to alter vulnerability flag data in private projects, potentially leading to inaccurate security status reporting or masking of real vulnerabilities.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade GitLab EE to a fixed version. Specifically, update to version 18.8.9 or later if you are using the 18.8 series, 18.9.5 or later for the 18.9 series, or 18.10.3 or later for the 18.10 series.
This will prevent authenticated users with auditor privileges from modifying vulnerability flag data in private projects due to incorrect authorization.