Vulnerability record · CVE-2026-105711 · published 22 October 2026
CVE-2026-105711: Gitlab vulnerability
Gitlab · Gitlab
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.0 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, when a merge request in a public project referenced a confidential issue from a private project, an authenticated user with no project membership could have read the confidential issue's title, due to a viewer-independent fragment cache key that incorrectly shared per-user-redacted rendered content across all users.
Description
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.0 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, when a merge request in a public project referenced a confidential issue from a private project, an authenticated user with no project membership could have read the confidential issue's title, due to a viewer-independent fragment cache key that incorrectly shared per-user-redacted rendered content across all users.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
Affected products
1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/ | Release NotesVendor Advisory |
| https://gitlab.com/gitlab-org/gitlab/-/work_items/632207 | Permissions Required |
| https://hackerone.com/reports/3963293 | Permissions Required |
Track CVE-2026-105711 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2026-105711), CISA KEV, FIRST EPSS (scores of 2026-11-11). This page is refreshed as NVD updates the record.