CVE-2026-105711 GitLab CVE debrief

Who should care

Defenders responsible for GitLab CE/EE deployments, particularly those with public projects and confidential issues, should assess exposure and apply patches or compensating controls as needed.

Why it matters

CVE-2026-105711 is a low-severity vulnerability in GitLab CE/EE that allows an authenticated user to read confidential issue titles under certain conditions. Defenders should prioritize patching affected versions and review access controls.

• An authenticated user with no project membership could potentially read confidential issue titles.
• Defenders should verify and apply patches for affected versions to prevent potential unauthorized access.
• GitLab administrators should review and update access controls for confidential issues in private projects.

Technical summary

The vulnerability affects GitLab CE/EE versions 15.0 to 19.5.0 and allows an authenticated user with no project membership to read confidential issue titles when a merge request in a public project references a confidential issue from a private project. This occurs due to a viewer-independent fragment cache key that incorrectly shared per-user-redacted rendered content across all users. Defenders should prioritize verifying and applying patches for affected versions and review access controls. The issue has been remediated in versions 19.3.6, 19.4.3, and 19.5.1.

Defensive priority

Defenders should prioritize verifying and applying patches for GitLab CE/EE versions 15.0 to 19.5.0, as an authenticated user with no project membership could potentially read confidential issue titles.

Recommended defensive actions

• Verify and apply patches for GitLab CE/EE versions 15.0 to 19.5.0
• Review and update access controls for confidential issues in private projects
• Monitor for potential unauthorized access to confidential issues
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including affected versions and a CVSS score of 3.5. GitLab has released patches for the issue. Defenders should verify and apply patches for GitLab CE/EE versions 15.0 to 19.5.0. The vulnerability allows an authenticated user with no project membership to read confidential issue titles when a merge request in a public project references a confidential issue from a private project. Evidence is limited to public sources and CVE details.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.