CVE-2026-2238

Analyzed Analyzed - Analysis Complete

Improper Authorization Leading to Confidential Issue Exposure in GitLab

Publication date: 2026-06-25

Last updated on: 2026-06-26

Assigner: GitLab Inc.

Description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.5 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an unauthenticated user to view confidential issue references on public projects due to improper authorization checks.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-06-25

Last Modified

2026-06-26

Generated

2026-07-15

AI Q&A

2026-06-25

EPSS Evaluated

2026-07-14

NVD

CVE-2026-2238

EUVD

EUVD-2026-39177

Affected Vendors & Products

Vendor	Product	Version / Range
gitlab	gitlab	From 19.0.0 (inc) to 19.0.3 (exc)
gitlab	gitlab	From 17.5.0 (inc) to 18.11.6 (exc)
gitlab	gitlab	19.1.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-862	The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

Executive Summary

This vulnerability in GitLab CE/EE affects versions from 17.5 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1. Under certain conditions, it could allow an unauthenticated user to view confidential issue references on public projects due to improper authorization checks.

Impact Analysis

The impact of this vulnerability is that unauthorized users could gain access to confidential information related to issues in public projects. This exposure could lead to information leakage, potentially compromising sensitive project details.

Compliance Impact

This vulnerability could allow an unauthenticated user to view confidential issue references on public projects due to improper authorization checks.

Exposure of confidential information may impact compliance with data protection regulations such as GDPR and HIPAA, which require safeguarding sensitive data and preventing unauthorized access.

However, the provided context does not explicitly discuss the impact on compliance with these or other common standards and regulations.

Mitigation Strategies

To mitigate this vulnerability, you should upgrade GitLab CE/EE to a fixed version. Specifically, update to version 18.11.6 or later if you are using the 17.5 to before 18.11.6 range, version 19.0.3 or later if you are using 19.0 to before 19.0.3, or version 19.1.1 or later if you are using 19.1 to before 19.1.1.

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

0/70