No advisories yet.
Solution
Upgrade to versions 19.3.6, 19.4.3, 19.5.1 or above.
Workaround
No workaround given by the vendor.
Fri, 30 Oct 2026 18:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 27 Oct 2026 14:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:* cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:* cpe:2.3:a:gitlab:gitlab:19.5.0:*:*:*:community:*:*:* cpe:2.3:a:gitlab:gitlab:19.5.0:*:*:*:enterprise:*:*:* |
Wed, 21 Oct 2026 23:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Use of Cache Containing Sensitive Information in GitLab | |
| First Time appeared |
Gitlab
Gitlab gitlab |
|
| Weaknesses | CWE-524 | |
| CPEs | cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Gitlab
Gitlab gitlab |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitLab
Published:
Updated: 2026-10-30T17:18:23.616Z
Reserved: 2026-10-05T18:35:06.853Z
Link: CVE-2026-105711
Updated: 2026-10-30T17:09:04.467Z
Status : Analyzed
Published: 2026-10-22T01:16:57.340
Modified: 2026-11-04T23:10:00.223
Link: CVE-2026-105711
No data.
OpenCVE Enrichment
Updated: 2026-10-22T08:00:03Z