Pipeline denial via branch-named tag collision
Published Sep 29, 2023 · Updated Apr 29, 2026
Denial of service in GitLab EE and CE before 16.2.8, 16.3 through 16.3.4, and 16.4.0 allows remote authenticated users to fail pipelines. GitLab permits a Developer to push a tag named refs/heads/main, causing pipeline ref resolution to withhold protected CI/CD variables. Developer access to a project with protected variables is required; affected pipelines lose those variables and can fail.
Summary
What happened
Denial of service in GitLab EE and CE before 16.2.8, 16.3 through 16.3.4, and 16.4.0 allows remote authenticated users to fail pipelines. GitLab permits a Developer to push a tag named refs/heads/main, causing pipeline ref resolution to withhold protected CI/CD variables. Developer access to a project with protected variables is required; affected pipelines lose those variables and can fail.
The record
- CVE
- CVE-2023-3917
- Published
- Sep 29, 2023
- Updated
- Apr 29, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-1287, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 29, 2023CVE publishedPublication date reported by the CVE source.
- Apr 29, 2026Record 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.2.8
- Affected versionversion=16.3 <16.3.5
- Affected versionversion=16.4 <16.4.1
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
- Public branch-named tag reproduction stepsproof 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