CVE-2025-9957
Authorization Bypass in GitLab CE/EE Allows Fork Prevention Bypass
Publication date: 2026-04-22
Last updated on: 2026-04-23
Assigner: GitLab Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gitlab | gitlab | From 18.10.0 (inc) to 18.10.4 (exc) |
| gitlab | gitlab | From 18.10.0 (inc) to 18.10.4 (exc) |
| gitlab | gitlab | From 11.2.0 (inc) to 18.9.6 (exc) |
| gitlab | gitlab | From 11.2.0 (inc) to 18.9.6 (exc) |
| gitlab | gitlab | 18.11.0 |
| gitlab | gitlab | 18.11.0 |
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 11.2 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1. Under certain conditions, it could allow an authenticated user with project owner permissions to bypass group fork prevention settings due to improper authorization checks.
How can this vulnerability impact me? :
The vulnerability allows a project owner to bypass group fork prevention settings, which could lead to unauthorized forking of projects within a group. This may result in unintended code duplication or exposure of project code to unauthorized forks, potentially impacting project confidentiality and control.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update GitLab CE/EE to a fixed version. Specifically, upgrade to version 18.9.6 or later if using the 18.9 series, 18.10.4 or later if using the 18.10 series, or 18.11.1 or later if using the 18.11 series. These versions contain the fix for the improper authorization checks that allowed bypassing group fork prevention settings.