Use of Cache Containing Sensitive Information in GitLab (CVE-2026-105711)
Published Last modified Sources: CVE.org, BSI
What is affected, what to do
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.
An exploit is publicly available. Update GitLab to version 19.3.6, GitLab to version 19.4.3, GitLab to version 19.5.1.
- Affected
- GitLab
lt 15.0..19.3.6 - GitLab
lt 19.4..19.4.3 - GitLab
lt 19.5..19.5.1
- GitLab
- Fixed in
- GitLab
19.3.6 - GitLab
19.4.3 - GitLab
19.5.1
- GitLab
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
3.5
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v3
3.5
CVSS v3
Severity Low on the scale from 0 to 10.
Source: CVE.org, BSI
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- Low
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 47.50 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- PoC (publicly reported)
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 3.5 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 3.5
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-524
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
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.
Source: NVD (NIST), cvelistv5, BSI CSAF, BSI WID Portal
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| GitLab | GitLab |
|
|
| Open Source | GitLab |
|
|
Weakness classes (CWE)
CWE-524Use of Cache Containing Sensitive Information
Base
The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere.
Entry at MITRE CWE-524
Public exploit references
Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.
| Source | Reference | Maturity | Published |
|---|---|---|---|
| Reference tagged as exploit | hackerone.com (opens in a new tab) | PoC (publicly reported)reported, not verified | — |
References & sources
- gitlab.comgitlab-org/gitlab/-/work_items/632207
- hackerone.comHackerOne Bug Bounty Report #3963293Technical description, Exploit, Permissions required
- docs.gitlab.comreleases/patches/patch-release-gitlab-19-5-1-released
Reanalysis & status changes
Chronological NVD audit events for this CVE — reanalyses, CVSS updates, CPE diffs.
New CVE Receivedcve@gitlab.com
- Description: after 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.
- CVSS V3.1: after AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
- CWE: after CWE-524
- Affected: after New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/105xxx/CVE-2026-105711.json">CVE-2026-105711</a>
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-105711"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-105711.svg?lang=en" alt="CVE-2026-105711 – NEOSEC Intel" height="20"></a>