GitLab Enterprise Edition up to 17.11.4/18.0.2/18.1.0 GraphQL authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.6 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in GitLab Enterprise Edition up to 17.11.4/18.0.2/18.1.0. This impacts an unknown function of the component GraphQL Handler. The manipulation results in authorization. This vulnerability was named CVE-2025-5846. The attack may be performed from remote. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability classified as problematic has been found in GitLab Enterprise Edition up to 17.11.4/18.0.2/18.1.0. Affected is some unknown functionality of the component GraphQL Handler. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on integrity. CVE summarizes:
An issue has been discovered in GitLab EE affecting all versions from 16.10 before 17.11.5, 18.0 before 18.0.3, and 18.1 before 18.1.1 that could have allowed authenticated users to assign unrelated compliance frameworks to projects by sending crafted GraphQL mutations that bypassed framework-specific permission checks.
The weakness was presented by Joern Schneeweisz. The advisory is available at gitlab.com. This vulnerability is traded as CVE-2025-5846 since 06/07/2025. The exploitability is told to be easy. It is possible to launch the attack remotely. Additional levels of successful authentication are necessary for exploitation. The technical details are unknown and an exploit is not available.
The vulnerability scanner Nessus provides a plugin with the ID 240625 (GitLab 16.10 < 17.11.5 / 18.0 < 18.0.3 / 18.1 < 18.1.1 (CVE-2025-5846)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 17.11.5, 18.0.3 or 18.1.1 eliminates this vulnerability.
The vulnerability is also documented in the databases at Tenable (240625) and EUVD (EUVD-2025-19172). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://gitlab.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.7VulDB Meta Temp Score: 2.7
VulDB Base Score: 2.7
VulDB Temp Score: 2.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 2.7
CNA Vector (GitLab): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 240625
Nessus Name: GitLab 16.10 < 17.11.5 / 18.0 < 18.0.3 / 18.1 < 18.1.1 (CVE-2025-5846)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Enterprise Edition 17.11.5/18.0.3/18.1.1
Timeline
06/07/2025 🔍06/26/2025 🔍
06/26/2025 🔍
06/26/2025 🔍
Sources
Vendor: gitlab.comAdvisory: gitlab.com
Researcher: Joern Schneeweisz
Status: Confirmed
CVE: CVE-2025-5846 (🔍)
GCVE (CVE): GCVE-0-2025-5846
GCVE (VulDB): GCVE-100-313938
EUVD: 🔍
Entry
Created: 06/26/2025 07:56Updated: 06/26/2025 15:16
Changes: 06/26/2025 07:56 (65), 06/26/2025 10:55 (1), 06/26/2025 15:16 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.