CVE-2025-14595
Improper Access Control in GitLab EE Exposes Security Metadata
Publication date: 2026-03-25
Last updated on: 2026-03-26
Assigner: GitLab Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gitlab | gitlab | From 18.9.0 (inc) to 18.9.3 (exc) |
| gitlab | gitlab | 18.10.0 |
| gitlab | gitlab | From 18.9.0 (inc) to 18.9.3 (exc) |
| gitlab | gitlab | 18.10.0 |
| gitlab | gitlab | From 18.6.0 (inc) to 18.8.7 (exc) |
| gitlab | gitlab | From 18.6.0 (inc) to 18.8.7 (exc) |
Helpful Resources
Exploitability
| 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
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in GitLab Enterprise Edition affects versions from 18.6 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1. It allows an authenticated user with the Planner role to view security category metadata and attributes in group security configuration due to improper access control under certain conditions.
How can this vulnerability impact me? :
The impact of this vulnerability is that a user with limited privileges (Planner role) could gain unauthorized access to sensitive security metadata and configuration attributes within GitLab groups. This could potentially expose security-related information that should be restricted, leading to information disclosure.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade GitLab EE to a fixed version. Specifically, update to version 18.8.7 or later if you are on the 18.8 branch, 18.9.3 or later if on the 18.9 branch, or 18.10.1 or later if on the 18.10 branch.
This vulnerability affects versions from 18.6 before the fixed versions mentioned, and it allows an authenticated user with Planner role to view security category metadata due to improper access control.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows an authenticated user with Planner role to view security category metadata and attributes in group security configuration due to improper access control.
Exposure of security-related metadata could potentially lead to unauthorized disclosure of sensitive information, which may impact compliance with standards and regulations such as GDPR or HIPAA that require strict access controls and protection of sensitive data.
However, the provided information does not explicitly state the direct impact on compliance with these standards.