Approval-policy bypass via editable rule identifiers
Published Aug 13, 2025 · Updated Aug 13, 2025
Authorization bypass in GitLab EE allows remote authenticated users with Developer access to remove merge request approval requirements. The merge request update endpoint accepts a policy-originated approval rule identifier and edits that hidden rule because default settings do not prevent such changes. Developer access to a contained project is sufficient, allowing a merge request to proceed without its policy-required approval.
Summary
What happened
Authorization bypass in GitLab EE allows remote authenticated users with Developer access to remove merge request approval requirements. The merge request update endpoint accepts a policy-originated approval rule identifier and edits that hidden rule because default settings do not prevent such changes. Developer access to a contained project is sufficient, allowing a merge request to proceed without its policy-required approval.
The record
- CVE
- CVE-2025-8770
- Published
- Aug 13, 2025
- Updated
- Aug 13, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-639, T1562.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 13, 2025CVE publishedPublication date reported by the CVE source.
- Aug 13, 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=18.0 <18.0.6
- Affected versionversion=18.1 <18.1.4
- Affected versionversion=18.2 <18.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.
Weakness, pattern, technique
Public exploit references
- GitLab approval-policy bypass 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