CVE-2026-105711
Use of Cache Containing Sensitive Information in GitLab
- Low 3.5
- A public exploit reference is listed
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.
Key facts
- Published
- 21 Oct 2026
- Last changed
- 30 Oct 2026
- Assigned by
- GitLab
- EPSS
- 0.217% likely to be exploited in the next 30 days, higher than 12.227% of CVEs (scores for 17 Nov 2026)
- SSVC (CISA)
- Exploitation: none; Automatable: no; Technical impact: partial
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 3.5CVSS 3.1, Lowfrom the CNA (GitLab)
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
What to do
- Upgrade to versions 19.3.6, 19.4.3, 19.5.1 or above.CNA solution statement
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| GitLab | GitLab |
|
Timeline
- 21 Oct 2026 Published