---
id: "CVE-2026-105711"
kind: "vulnerability"
aliases: ["CVE-2026-105711"]
title: "GitLab CE/EE: cached merge request previews leaked confidential issue titles"
severity: "low"
cvss: 3.5
epss: 0.00212
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["gitlab", "gitlab-ce", "gitlab-ee", "infrastructure", "self-hosted"]
not_affected_if: ["all-projects-private", "gitlab-com-managed"]
published_at: "2026-10-22T01:16:57+00:00"
first_seen_at: "2026-10-23T21:57:29+00:00"
updated_at: "2026-10-25T04:45:40+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-105711", "first_seen_at": "2026-10-23T21:57:29+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-105711", "first_seen_at": "2026-10-24T07:15:52+00:00"}]
---

# GitLab CE/EE: cached merge request previews leaked confidential issue titles

GitLab's rendered-content cache reused a redacted view of a merge request reference across users, so an authenticated user with no project membership could read the title of a confidential issue in a private project. An attacker gets only the issue title, not its body or other data.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed GitLab version with `gitlab-rake gitlab:env:info` or the version shown under the Admin Area.
- Confirm whether the instance is GitLab CE or EE and whether it runs on a version from 15.0 through the fixed releases listed below.

## Fix

- Upgrade GitLab CE/EE to `19.3.6`, `19.4.3`, or `19.5.1` depending on the release line you run.
- Upgrade to any later patch release on the same line.

## Timeline

- 2026-10-23T21:57:29+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-105711
- 2026-10-24T07:15:52+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-105711

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_