CVE-2025-2615
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 16.7.0 (inc) to 18.3.6 (exc) |
| gitlab | gitlab | From 16.7.0 (inc) to 18.3.6 (exc) |
| gitlab | gitlab | From 18.4.0 (inc) to 18.4.4 (exc) |
| gitlab | gitlab | From 18.4.0 (inc) to 18.4.4 (exc) |
| gitlab | gitlab | From 18.5.0 (inc) to 18.5.2 (exc) |
| gitlab | gitlab | From 18.5.0 (inc) to 18.5.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-201 | The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in GitLab CE/EE versions before 18.3.6, 18.4.4, and 18.5.2 allowed a blocked user to access sensitive information by establishing GraphQL subscriptions through WebSocket connections.
How can this vulnerability impact me? :
The vulnerability could allow a blocked user to bypass restrictions and access sensitive information, potentially leading to unauthorized data exposure.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade GitLab CE/EE to a fixed version: 18.3.6 or later for the 18.3 series, 18.4.4 or later for the 18.4 series, or 18.5.2 or later for the 18.5 series. This will prevent blocked users from accessing sensitive information via GraphQL subscriptions over WebSocket connections.