Protected-branch schedule modification via missing authorization
Published Dec 1, 2023 · Updated Nov 20, 2025
Incorrect authorization in GitLab allows remote authenticated users with Developer access to redirect a pipeline schedule to a protected branch. The pipeline-schedule update path accepts a change from an unprotected branch without correctly enforcing protected-branch access control. Developer project membership is required, and the unauthorized schedule change compromises pipeline configuration integrity.
Summary
What happened
Incorrect authorization in GitLab allows remote authenticated users with Developer access to redirect a pipeline schedule to a protected branch. The pipeline-schedule update path accepts a change from an unprotected branch without correctly enforcing protected-branch access control. Developer project membership is required, and the unauthorized schedule change compromises pipeline configuration integrity.
The record
- CVE
- CVE-2023-4317
- Published
- Dec 1, 2023
- Updated
- Nov 20, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-863
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 1, 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=16.5 <16.5.3
- Affected versionversion=16.6 <16.6.1
- Affected versionversion=9.2 <16.4.3
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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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