CVE-2025-11702: 
GitLab vulnerability analysis and mitigation

GitLab has disclosed a high-severity vulnerability (CVE-2025-11702) affecting GitLab Enterprise Edition (EE). The vulnerability was discovered on October 22, 2025, impacting all versions from 17.1 before 18.3.5, 18.4 before 18.4.3, and 18.5 before 18.5.1. This improper access control issue in the runner API could potentially allow authenticated users with specific permissions to compromise the security of project runners (GitLab Advisory).

The vulnerability has been assigned a CVSS v3.1 base score of 8.5 (High), with the following vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H. The scoring indicates that the vulnerability requires network access, has high attack complexity, needs low privileges, requires no user interaction, and can result in high impacts to confidentiality, integrity, and availability with changed scope (GitLab Advisory, AttackerKB).

If successfully exploited, this vulnerability could allow attackers to gain control over build infrastructure, intercept CI/CD secrets, or inject malicious code into automated pipelines. This represents a critical risk for enterprises running shared runners across multiple projects, potentially compromising the entire CI/CD infrastructure (Security Online).

GitLab has released patches in versions 18.5.1, 18.4.3, and 18.3.5 for Enterprise Edition (EE). Organizations are strongly advised to upgrade immediately to these patched versions. GitLab.com is already running the patched version, and GitLab Dedicated customers do not need to take action (GitLab Advisory).