CVE-2026-5377

Received Received - Intake

Improper Access Control in GitLab Issues Disclosure

Publication date: 2026-04-22

Last updated on: 2026-04-23

Assigner: GitLab Inc.

Description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.11 before 18.11.1 that could have allowed an authenticated user to access titles of confidential or private issues in public projects due to improper access control in the issue description rendering process.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-04-22

Last Modified

2026-04-23

Generated

2026-07-06

AI Q&A

2026-04-22

EPSS Evaluated

2026-07-05

NVD

CVE-2026-5377

EUVD

EUVD-2026-25044

Affected Vendors & Products

Vendor	Product	Version / Range
gitlab	gitlab	18.11.0
gitlab	gitlab	18.11.0

Helpful Resources

Exploitability

CWE

KEV

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

Mitigation Strategies

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.

Impact Analysis

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.

Executive Summary

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.

Compliance Impact

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.

Hi! I’m here to help you understand CVE-2026-5377. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70