CVE-2026-9807
Incorrect Authorization Enforcement in GitLab CE/EE
Publication date: 2026-05-28
Last updated on: 2026-05-28
Assigner: GitLab Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gitlab | gitlab_ce | From 18.9 (inc) to 18.10.7 (exc) |
| gitlab | gitlab_ce | From 18.11 (inc) to 18.11.4 (exc) |
| gitlab | gitlab_ce | From 19.0 (inc) to 19.0.1 (exc) |
| gitlab | gitlab_ee | From 18.9 (inc) to 18.10.7 (exc) |
| gitlab | gitlab_ee | From 18.11 (inc) to 18.11.4 (exc) |
| gitlab | gitlab_ee | From 19.0 (inc) to 19.0.1 (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 CE/EE affects versions from 18.9 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1. Under certain conditions, a blocked Project Access Token could still access private resources due to incorrect authorization enforcement.
How can this vulnerability impact me? :
The vulnerability could allow a blocked Project Access Token to continue accessing private resources, potentially exposing sensitive data or resources that should have been restricted.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade GitLab CE/EE to a fixed version. Specifically, update to GitLab CE/EE version 18.10.7 or later, 18.11.4 or later, or 19.0.1 or later, depending on your current version.