Developer protected-branch scheduling via ref-blind authorization
Published Aug 2, 2023 · Updated Nov 20, 2025
Missing authorization in affected GitLab CE/EE 16.x releases allows remote authenticated users to schedule pipelines on protected branches. Projects::PipelineSchedulesController authorizes against the project, while ProjectPolicy omits the target ref and its protected-branch merge permission. Developer access to the project is required; the demonstrated consequence is unauthorized schedule creation rather than broader repository access.
Summary
What happened
Missing authorization in affected GitLab CE/EE 16.x releases allows remote authenticated users to schedule pipelines on protected branches. Projects::PipelineSchedulesController authorizes against the project, while ProjectPolicy omits the target ref and its protected-branch merge permission. Developer access to the project is required; the demonstrated consequence is unauthorized schedule creation rather than broader repository access.
The record
- CVE
- CVE-2023-2022
- Published
- Aug 2, 2023
- Updated
- Nov 20, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-862, T1053
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 2, 2023CVE publishedPublication date reported by the CVE source.
- Nov 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <16.0.8
- Affected versionversion=16.1.0 <16.1.3
- Affected versionversion=16.2.0 <16.2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Protected-branch pipeline schedule reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo