Policy bypass via unchecked protected-branch rename
Published Feb 7, 2024 · Updated Apr 24, 2026
Missing authorization in affected GitLab EE 16.x releases allows remote authenticated Maintainers to bypass protected-branch policy. ProtectedBranches::UpdateService accepts a protected-branch name change without enforcing block_branch_modification, moving the branch outside the policy match. Maintainer access and an enabled merge request approval policy are required; the bypass can permit unreviewed code changes.
Summary
What happened
Missing authorization in affected GitLab EE 16.x releases allows remote authenticated Maintainers to bypass protected-branch policy. ProtectedBranches::UpdateService accepts a protected-branch name change without enforcing block_branch_modification, moving the branch outside the policy match. Maintainer access and an enabled merge request approval policy are required; the bypass can permit unreviewed code changes.
The record
- CVE
- CVE-2023-6840
- Published
- Feb 7, 2024
- Updated
- Apr 24, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-862, T1562.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 7, 2024CVE publishedPublication date reported by the CVE source.
- Apr 24, 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=16.4 <16.6.7
- Affected versionversion=16.7 <16.7.5
- Affected versionversion=16.8 <16.8.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.
Weakness, pattern, technique
Public exploit references
- Protected-branch rename 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