Authenticated deployment-data disclosure via missing authorization
Published May 27, 2026 · Updated May 27, 2026
Missing authorization in affected GitLab EE releases allows remote authenticated users with Developer access to read sensitive deployment data. GitLab has disclosed only that the flaw resides in Operations, where authorization checks fail to restrict sensitive project deployment data. Developer-role access to an affected project is required; the bounded impact is disclosure, with no reported ability to alter data or interrupt service.
Summary
What happened
Missing authorization in affected GitLab EE releases allows remote authenticated users with Developer access to read sensitive deployment data. GitLab has disclosed only that the flaw resides in Operations, where authorization checks fail to restrict sensitive project deployment data. Developer-role access to an affected project is required; the bounded impact is disclosure, with no reported ability to alter data or interrupt service.
The record
- CVE
- CVE-2026-2601
- Published
- May 27, 2026
- Updated
- May 27, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-862, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 27, 2026CVE publishedPublication date reported by the CVE source.
- May 27, 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.5 <18.10.7
- Affected versionversion=18.11 <18.11.4
- Affected versionversion=19.0 <19.0.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.
Public exploit references
- HackerOne Bug Bounty Report 3556381proof of concept · unverified
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