---
id: CVE-2023-5009
title: Incorrect Authorization in GitLab
summary: >-
  An issue has been discovered in GitLab EE affecting all versions starting from
  13.12 before 16.2.7, all versions starting from 16.3 before 16.3.4. It was
  possible for an attacker to run pipeline jobs as an arbitrary user via
  scheduled se…
severity: high
cvss: 8.2
cvssVector: 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N'
cvssSource: cna
cwe:
  - CWE-863
vendor: GitLab
product: GitLab
affected:
  - GitLab >= 13.12 < 16.2.7
  - GitLab >= 16.3 < 16.3.4
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: total
  timestamp: '2025-02-26T21:51:08.131679Z'
published: '2023-09-19'
updated: '2026-10-28'
sourceUpdated: '2026-10-28T11:39:50.305Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2023-5009'
references:
  - url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/425304'
    label: 'GitLab Issue #425304'
  - url: 'https://hackerone.com/reports/2147126'
    label: 'HackerOne Bug Bounty Report #2147126'
tags:
  - cve.org
epss: 0.09651
epssPercentile: 0.95464
ingestedAt: '2026-10-28T12:10:35.156Z'
---

## Overview

An issue has been discovered in GitLab EE affecting all versions starting from 13.12 before 16.2.7, all versions starting from 16.3 before 16.3.4. It was possible for an attacker to run pipeline jobs as an arbitrary user via scheduled security scan policies. This was a bypass of [CVE-2023-3932](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-3932) showing additional impact.

## Affected

- `GitLab >= 13.12 < 16.2.7`
- `GitLab >= 16.3 < 16.3.4`

## Remediation

Upgrade to versions 16.2.7, 16.3.4 or above For those users unable to upgrade for those versions, you can mitigate the vulnerability by having at most one of those two features turned on at one time: - [Direct transfers](https://docs.gitlab.com/ee/administration/settings/import_and_export_settings.html#enable-migration-of-groups-and-projects-by-direct-transfer) - [Security policies](https://docs.gitlab.com/ee/user/application_security/policies/scan-execution-policies.html)