Private issue disclosure via unchecked epic links
Published Sep 29, 2026 · Updated Sep 29, 2026
GitLab CE/EE 19.0 through 19.2.6, 19.3 through 19.3.2, and 19.4.0 expose private child issues to remote authenticated users. The Epic Issues REST API omits authorization checks on work items linked to a visible epic, returning issue titles and descriptions from projects the caller cannot access. Exploitation requires an account and a visible epic linked to otherwise inaccessible issues; the reported consequence is disclosure, not modification.
Summary
What happened
GitLab CE/EE 19.0 through 19.2.6, 19.3 through 19.3.2, and 19.4.0 expose private child issues to remote authenticated users. The Epic Issues REST API omits authorization checks on work items linked to a visible epic, returning issue titles and descriptions from projects the caller cannot access. Exploitation requires an account and a visible epic linked to otherwise inaccessible issues; the reported consequence is disclosure, not modification.
The record
- CVE
- CVE-2026-8937
- Published
- Sep 29, 2026
- Updated
- Sep 29, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-862, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 29, 2026CVE publishedPublication date reported by the CVE source.
- Sep 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=19.0 <19.2.7
- Affected versionversion=19.3 <19.3.3
- Affected versionversion=19.4 <19.4.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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started