CVE-2026-105711 Use of Cache Containing Sensitive Information in GitLab
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2026-105711?
CVE-2026-105711 is a low-severity vulnerability in Gitlab Gitlab, published on 21 Oct 2026.
Official 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.
Weakness: CWE-524
Which versions are affected by CVE-2026-105711?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 15.0.0 | 19.3.6, 19.4.3, 19.5.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2026-105711?
Upgrade gitlab to a fixed version for your release line: 19.3.6, 19.4.3 or 19.5.1.
Is CVE-2026-105711 being exploited?
There is no known exploitation of CVE-2026-105711 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as BIT-gitlab-2026-105711, GHSA-5jh8-pw64-jw5v.