Vulnerabilities

GitLab Patches Critical Pipeline Execution Vulnerability

GitLab has released security updates to address a critical-severity vulnerability allowing an attacker to run pipelines as another user.

GitLab has released security updates to address a critical-severity vulnerability allowing an attacker to run pipelines as another user.

DevOps platform GitLab this week announced the release of security updates that address a critical-severity vulnerability allowing an attacker to run pipelines as another user.

Tracked as CVE-2023-5009 (CVSS score of 9.6) and affecting all GitLab Enterprise Edition (EE) versions before 16.2.7 and GitLab Community Edition (CE) versions before 16.3.4, the bug is a bypass of another flaw, CVE-2023-3932, which was addressed in August 2023.

According to GitLab’s advisory, the issue allows “an attacker to run pipelines as an arbitrary user via scheduled security scan policies”.

The original vulnerability, CVE-2023-3932, was reported via GitLab’s HackerOne bug bounty program by a researcher who explained that the attacker could trigger the issue via the scan execution policy.

The bug could be triggered without any user interaction, but the attacker needed to know the victim’s GitLab username and the name of a victim’s internal or members-only project.

By exploiting the flaw, the attacker could gain access to projects containing private code, the researcher explained.

Advertisement. Scroll to continue reading.

CVE-2023-5009 too was reported through the HackerOne platform, and GitLab encourages users to update to GitLab CE and EE versions 16.3.4 and 16.2.7, which resolve the flaw.

However, the code hosting platform also notes that for GitLab versions prior to 16.2 the vulnerability only exists if the ‘Direct transfers’ and ‘Security policies’ features are enabled at the same time.

To mitigate the flaw, users that cannot upgrade to a patched version of GitLab can disable one or both these features.

“We strongly recommend that all installations running a version affected by the issues are upgraded to the latest version as soon as possible,” GitLab notes.

The code hosting platform makes no mention of this vulnerability being exploited in malicious attacks.

Related: GitLab Security Update Patches Critical Vulnerability

Related: GitLab Patches Critical Remote Code Execution Vulnerability

Related: Critical Account Takeover Vulnerability Patched in GitLab Enterprise Edition

Related Content

Vulnerabilities

The critical-severity path traversal flaw allows unauthenticated attackers to read arbitrary files from the GitLab server.

Vulnerabilities

CVE-2026-19478 can be exploited without authentication to modify or delete public projects and user data.

Vulnerabilities

The security defect allows unauthenticated attackers to modify or delete user data and public projects.

Vulnerabilities

The latest GitLab CE/EE updates address 13 vulnerabilities, including three high-severity defects.

Vulnerabilities

Fixes were rolled out for over two dozen vulnerabilities, including critical- and high-severity bugs.

Data Breaches

Hackers claim to have stolen 28,000 private repositories, including data associated with major companies that use Red Hat services.

Vulnerabilities

GitLab and Atlassian have released patches for over a dozen vulnerabilities in their products, including high-severity bugs.

Vulnerabilities

The latest GitLab update resolves eight vulnerabilities, including critical- and high-severity pipeline execution flaws.

Copyright © 2026 SecurityWeek ®, a Wired Business Media Publication. All Rights Reserved.

Exit mobile version