CVE-2026-105711: gitlab — Fix

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.

Is your site exposed to CVE-2026-105711?

Run a free security scan — no signup, results in seconds.

CVSS v3.1 Score

3.5

LOW

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N

EPSS — Exploit Prediction

0.0022

Probability of exploitation

0.12%

Percentile rank

EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.

Weakness Type (CWE)

CWE-524 CWE-524

Affected Products

Vendor	Product	Versions
gitlab	gitlab	15.0.0 — 19.3.6
gitlab	gitlab	15.0.0 — 19.3.6
gitlab	gitlab	19.4.0 — 19.4.3
gitlab	gitlab	19.4.0 — 19.4.3
gitlab	gitlab	All
gitlab	gitlab	All

References

Advisories & Patches

https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/

Other References

https://gitlab.com/gitlab-org/gitlab/-/work_items/632207 https://hackerone.com/reports/3963293

Frequently Asked Questions

What is CVE-2026-105711? +

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. It has a CVSS v3.1 base score of 3.5 (LOW).

How severe is CVE-2026-105711? +

CVE-2026-105711 has a CVSS v3.1 score of 3.5 out of 10, rated LOW. This is a low-severity vulnerability with limited impact. The EPSS score is 0.0022, placing it in the 0th percentile for exploitation probability.

What products are affected by CVE-2026-105711? +

CVE-2026-105711 affects products from gitlab, specifically: gitlab. Check the affected products table above for specific version ranges.

How do I check if I'm vulnerable to CVE-2026-105711? +

You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.

Related Vulnerabilities

CVE-2026-108088

** UNSUPPORTED WHEN ASSIGNED ** Use of cache containing sensitive information vulnerability in Apache Cocoon. When using the cache on …

CVE-2026-19202

A caching flaw in the toolbox-core package of the mcp-toolbox-sdk-python SDK causes the same Google ID token to be cached …

CVE-2026-89186

Use of Cache Containing Sensitive Information in ZenHive mpp allows a shared HTTP cache to store a paid response and …

CVE-2026-92443

The caching plugins in Kong Gateway Enterprise and Kong AI Gateway may serve a response cached for a request carrying …

CVE-2026-92545

The proxy-cache and proxy-cache-advanced plugins in Kong Gateway Enterprise and Kong AI Gateway omit the request hostname from the cache …

CVE-2026-123041

The request-callout plugin in Kong Gateway Enterprise and Kong AI Gateway omits callout headers not sent by the client from …

CVE-2026-105711