Vulnerability in GitLab
CVE-2026-105711
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 3.5 (Low). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
Weakness classification (CWE)
References
- gitlab.com/gitlab-org/gitlab/-/work_items/632207
- hackerone.com/reports/3963293 (technical-description, permissions-required, exploit)
- docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/
Frequently asked questions
- What is CVE-2026-105711?
- CVE-2026-105711 is a low-severity vulnerability in GitLab, classified under Use of Cache Containing Sensitive Information. CVSS score: 3.5/10. Published 2026-10-22.
- How severe is CVE-2026-105711?
- Low severity. CVSS v3 base score is 3.5 out of 10.