GitLab Community Edition/Enterprise Edition up to 18.5.4/18.6.2/18.7.0 GraphQL Runner Association insufficient granularity of access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in GitLab Community Edition and Enterprise Edition up to 18.5.4/18.6.2/18.7.0. Impacted is an unknown function of the component GraphQL Runner Association Handler. Performing a manipulation results in insufficient granularity of access control. This vulnerability is reported as CVE-2025-11246. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in GitLab Community Edition and Enterprise Edition up to 18.5.4/18.6.2/18.7.0. This affects an unknown functionality of the component GraphQL Runner Association Handler. The manipulation with an unknown input leads to a insufficient granularity of access control vulnerability. CWE is classifying the issue as CWE-1220. The product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. However, implemented access controls lack required granularity, which renders the control policy too broad because it allows accesses from unauthorized agents to the security-sensitive assets. This is going to have an impact on integrity, and availability. The summary by CVE is:
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.4 before 18.5.5, 18.6 before 18.6.3, and 18.7 before 18.7.1 that could have allowed an authenticated user with specific permissions to remove all project runners from unrelated projects by manipulating GraphQL runner associations.
The weakness was disclosed by pwnie as 573728. The advisory is shared at gitlab.com. This vulnerability is uniquely identified as CVE-2025-11246 since 10/02/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available.
The vulnerability scanner Nessus provides a plugin with the ID 294813 (Linux Distros Unpatched Vulnerability : CVE-2025-11246), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 18.5.5, 18.6.3 or 18.7.1 eliminates this vulnerability. The upgrade is hosted for download at about.gitlab.com.
The vulnerability is also documented in the databases at Tenable (294813) and CERT Bund (WID-SEC-2026-0037). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- Open Source GitLab
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: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.4
VulDB Temp Score: 5.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.4
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: Insufficient granularity of access controlCWE: CWE-1220 / CWE-284 / CWE-266
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: 294813
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2025-11246
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Community Edition/Enterprise Edition 18.5.5/18.6.3/18.7.1
Timeline
10/02/2025 CVE reserved01/09/2026 Advisory disclosed
01/09/2026 VulDB entry created
01/23/2026 VulDB entry last update
Sources
Vendor: gitlab.comAdvisory: 573728
Researcher: pwnie
Status: Confirmed
CVE: CVE-2025-11246 (🔒)
GCVE (CVE): GCVE-0-2025-11246
GCVE (VulDB): GCVE-100-340257
CERT Bund: WID-SEC-2026-0037 - GitLab CE und EE: Mehrere Schwachstellen
Entry
Created: 01/09/2026 12:27Updated: 01/23/2026 09:13
Changes: 01/09/2026 12:27 (67), 01/12/2026 02:42 (7), 01/23/2026 09:13 (2)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.