CVE-2026-5377
Improper Access Control in GitLab Issues Disclosure
Publication date: 2026-04-22
Last updated on: 2026-04-23
Assigner: GitLab Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gitlab | gitlab | 18.11.0 |
| gitlab | gitlab | 18.11.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-863 | The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :
The vulnerability could lead to unauthorized disclosure of sensitive information by exposing titles of confidential or private issues to users who should not have access to them. This may result in information leakage within public projects.
Can you explain this vulnerability to me?
This vulnerability in GitLab CE/EE versions from 18.11 before 18.11.1 allows an authenticated user to access the titles of confidential or private issues in public projects. This happens because of improper access control during the rendering process of issue descriptions.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade GitLab CE/EE to version 18.11.1 or later, as the issue has been remediated starting from that version.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability could allow an authenticated user to access titles of confidential or private issues in public projects due to improper access control. Such unauthorized access to confidential information may lead to non-compliance with data protection regulations like GDPR or HIPAA, which require strict controls over access to sensitive data.
However, the CVE description does not explicitly mention compliance impacts or regulatory considerations.