Reporter-level approval-rule reset via missing authorization
Published Aug 26, 2026 · Updated Aug 26, 2026
Improper authorization in GitLab EE 13.1 through 19.1.6, 19.2 through 19.2.4, and 19.3.0 allows remote authenticated users to reset approval rules. The vendor has not disclosed the affected handler or the authorization check omitted before the approval-rule reset is applied. Exploitation requires reporter-role access, authorship of the merge request, user interaction, and unspecified additional conditions; the reported consequence is an integrity-only change to approval requirements.
Summary
What happened
Improper authorization in GitLab EE 13.1 through 19.1.6, 19.2 through 19.2.4, and 19.3.0 allows remote authenticated users to reset approval rules. The vendor has not disclosed the affected handler or the authorization check omitted before the approval-rule reset is applied. Exploitation requires reporter-role access, authorship of the merge request, user interaction, and unspecified additional conditions; the reported consequence is an integrity-only change to approval requirements.
The record
- CVE
- CVE-2026-7487
- Published
- Aug 26, 2026
- Updated
- Aug 26, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 26, 2026CVE publishedPublication date reported by the CVE source.
- Aug 26, 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=13.1 <19.1.7
- Affected versionversion=19.2 <19.2.5
- Affected versionversion=19.3 <19.3.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
No sourced classifications are available.
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