Use of Cache Containing Sensitive Information in GitLab
Severity and exploitation
KEV coverage does not rule out exploitation.
Assessment vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:NSeverity
low3.5CVSS measures technical severity, not the likelihood of an attack.
Known exploitation
Not listed in the checked CISA KEV catalog
Absence from CISA KEV does not rule out attacks.
Public exploit
Exploit reference published
Source-linked evidence; not proof of attacks in the wild or independent validation.
Remediation
Source guidance available
Review the recorded instructions. Guidance may be a workaround rather than a fixed version.
What this means
GitLab CE/EE versions 15.0 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 have a weakness where an authenticated user with no project membership could read a confidential issue's title due to a cache containing sensitive information. The issue occurs when a merge request in a public project references a confidential issue from a private project. An authenticated user can access the sensitive information.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Attack conditions
No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.
Review supporting sources →Affected versions
Check the exact model, release, and any platform requirements against your installation.
GitLab · GitLab
GitLab
3 ranges
GitLab · GitLab
GitLab
Compare with this publisher’s ranges. This does not inspect your installation.
affected
15.0 → before 19.3.6
semver versions
19.4 → before 19.4.3
semver versions
19.5 → before 19.5.1
semver versions
Other versions: unaffected
Product identifiers (CPE)
cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*What to do
Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.
Upgrade to versions 19.3.6, 19.4.3, 19.5.1 or above.
cve.new guidance unless attributed to a publisher. This page does not inspect your installation.
Public exploit evidence
The sources identify public exploit references. We have not independently tested them; their availability does not establish exploitation in the wild.
hackerone.com/reports/3963293 ↗Attributed to GitLabOriginal source description
Read the full publisher 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.
References
3 sourcesInside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-105711View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 2
Assigning organization
Additional data publisher
Timeline
All times UTCAdvisory published
Publication date supplied by the source.
Source updated
Latest modification date supplied by the source.
Last imported by cve.new
Latest catalog import, not the date we first saw this advisory.
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.