CVE-2026-105711

Use of Cache Containing Sensitive Information in GitLab

LOW
3.5
CVSS Score
Published: October 21, 2026 at 11:34 PM UTC
Updated: October 30, 2026 at 06:17 PM UTC
1 product affected across 1 vendorGitLab

Using GitLab by GitLab?

Get instant alerts when new vulnerabilities affect GitLab - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
LOW3.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

15.0.0 ≤ v < 19.3.619.4.0 ≤ v < 19.4.319.5.0

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (3)

Technical DescriptionExploitPermissions Required
Source: cverecord
https://hackerone.com/reports/3963293

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

3.5LOWGitLab
Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
LOW
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-524

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card