CVE-2025-11990
BaseFortify
Publication date: 2025-11-15
Last updated on: 2025-11-19
Assigner: GitLab Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gitlab | gitlab | From 18.4.0 (inc) to 18.4.4 (exc) |
| gitlab | gitlab | From 18.5.0 (inc) to 18.5.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
| CWE-177 | The product does not properly handle when all or part of an input has been URL encoded. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in GitLab EE versions before 18.4.4 and 18.5.2 allows an authenticated user to obtain CSRF tokens by exploiting improper input validation in repository references combined with weaknesses in redirect handling.
How can this vulnerability impact me? :
An attacker who is authenticated could gain CSRF tokens, which might be used to perform unauthorized actions on behalf of a user, potentially leading to limited confidentiality impact but no integrity or availability impact.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade GitLab EE to version 18.4.4 or later if you are running any version from 18.4 before 18.4.4, or to version 18.5.2 or later if you are running any version from 18.5 before 18.5.2. This update addresses the issue related to CSRF token exposure through improper input validation and redirect handling.