Unapproved production deployments via post-modification access checks
Published Sep 16, 2026 · Updated Sep 16, 2026
Improper access control in GitLab EE allows remote authenticated users to disable protected-environment deployment approvals. The approval-rule workflow performs its authorization check only after modifying the protected resource. Owner or Maintainer permissions and unspecified additional conditions are required, after which unapproved deployments can reach production.
Summary
What happened
Improper access control in GitLab EE allows remote authenticated users to disable protected-environment deployment approvals. The approval-rule workflow performs its authorization check only after modifying the protected resource. Owner or Maintainer permissions and unspecified additional conditions are required, after which unapproved deployments can reach production.
The record
- CVE
- CVE-2026-86341
- Published
- Sep 16, 2026
- Updated
- Sep 16, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- T1562.001
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Sep 16, 2026CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=17.1 <19.1.8
- Affected versionversion=19.2 <19.2.6
- Affected versionversion=19.3 <19.3.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
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