Protected-environment modification via missing deploy-access check
Published Apr 8, 2026 · Updated Apr 8, 2026
Incorrect authorization in GitLab EE allows remote authenticated users with Developer access to alter protected environment settings. The PUT environments API checked project-level update permission but failed to authorize the targeted environment against its protected-environment deploy policy. A Developer who belonged to the project but lacked deploy access could change fields such as the external URL, deployment tier, or description.
Summary
What happened
Incorrect authorization in GitLab EE allows remote authenticated users with Developer access to alter protected environment settings. The PUT environments API checked project-level update permission but failed to authorize the targeted environment against its protected-environment deploy policy. A Developer who belonged to the project but lacked deploy access could change fields such as the external URL, deployment tier, or description.
The record
- CVE
- CVE-2026-1752
- Published
- Apr 8, 2026
- Updated
- Apr 8, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-863, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 8, 2026CVE publishedPublication date reported by the CVE source.
- Apr 8, 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=11.3 <18.8.9
- Affected versionversion=18.10 <18.10.3
- Affected versionversion=18.9 <18.9.5
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