CVE-2026-105711
Use of Cache Containing Sensitive Information in GitLab
Reported by gitlab · Published October 21, 2026
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| gitlab | gitlab | 19.5.1, 19.4.3, 19.3.6 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| GitLab | GitLab | 15.0, 19.4, 19.5 |
| GitLab | GitLab | 15.0, 19.4, 19.5 |
Timeline
- Oct 21, 2026 CVE Published
- Oct 22, 2026 EPSS Score (3 in total, the first dated here)
- Oct 22, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-105711
vulnetix vdb fixes CVE-2026-105711Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-105711/fixes/registry"The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- HackerOne Bug Bounty Report #3963293 technical-descriptionexploitpermissions-required