Authenticated information exposure via internal requests
Published Jul 29, 2026 · Updated Jul 29, 2026
Information exposure in affected GitLab CE/EE releases allows remote authenticated users to read unauthorized information via internal requests. Workhorse performs insufficient access control during internal request handling, but GitLab has not disclosed the affected path, failed authorization operation, or exposed data classes. Affected lines are 10.1.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1; Developer access and high-complexity conditions are required.
Summary
What happened
Information exposure in affected GitLab CE/EE releases allows remote authenticated users to read unauthorized information via internal requests. Workhorse performs insufficient access control during internal request handling, but GitLab has not disclosed the affected path, failed authorization operation, or exposed data classes. Affected lines are 10.1.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1; Developer access and high-complexity conditions are required.
The record
- CVE
- CVE-2026-6267
- Published
- Jul 29, 2026
- Updated
- Jul 29, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-201
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 29, 2026CVE publishedPublication date reported by the CVE source.
- Jul 29, 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=10.1.0 <19.0.5
- Affected versionversion=19.1 <19.1.3
- Affected versionversion=19.2 <19.2.1
What conditions does exploitation require?
What is affected?
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