What is the CVSS score of CVE-2025-14595?

CVE-2025-14595 has a CVSS 3.1 base score of 4.3 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N. EPSS exploitation probability: 0.0%.

Which versions of Gitlab are affected by CVE-2025-14595?

Organizations using GitLab EE affecting all should be aware of moderate risk from CVE-2025-14595, a missing authorization vulnerability rated CVSS 4.3.. A patch is available.

Is there a public PoC exploit available for CVE-2025-14595?

Yes, a public proof-of-concept exploit is available for CVE-2025-14595. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2025-14595?

Within 30 days: Identify affected systems running GitLab EE affecting all and apply vendor patches as part of regular patch cycle. Monitor vendor channels for patch availability.

Gitlab CVE-2025-14595

EUVD-2025-208995 MEDIUM

Missing Authorization (CWE-862)

2026-03-25 GitLab

GHSA-8jj8-qh37-33q3

Gitlab Authentication Bypass

4.3

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

4.3 MEDIUM

AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Lifecycle Timeline

Patch available

Apr 16, 2026 - 05:29 EUVD

18.8.7,18.9.3,18.10.1

PoC Detected

Mar 26, 2026 - 18:28 vuln.today

Public exploit code

EUVD ID Assigned

Mar 25, 2026 - 16:47 euvd

EUVD-2025-208995

Analysis Generated

Mar 25, 2026 - 16:47 vuln.today

CVE Published

Mar 25, 2026 - 16:34 nvd

MEDIUM 4.3

DescriptionCVE.org

GitLab has remediated an issue in GitLab EE affecting all versions from 18.6 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1 that under certain conditions could have allowed an authenticated user with Planner role to view security category metadata and attributes in group security configuration due to improper access control

AnalysisAI

An improper access control vulnerability in GitLab EE allows authenticated users with the Planner role to view sensitive security category metadata and attributes in group security configurations they should not have access to. Affected versions include GitLab 18.6 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1. While the CVSS score is moderate at 4.3 (low confidentiality impact), a publicly available proof-of-concept exists and the vulnerability represents a straightforward privilege escalation through role-based access control bypass.

Technical ContextAI

This vulnerability is rooted in CWE-862: Missing Authorization, which occurs when a software system fails to properly enforce access control policies at the application level. The issue affects GitLab EE's group security configuration module, specifically the security category metadata display logic. The Planner role in GitLab is designed with limited permissions for planning and scheduling features, but the flawed authorization checks in the security configuration endpoint allow Planner-role users to bypass role-based access controls (RBAC) and retrieve security-sensitive metadata that should be restricted to higher-privileged roles such as Owners or Security Administrators. The vulnerability affects GitLab instances running the affected versions as identified in CPE notation cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*, requiring only network access and valid user credentials to exploit.

RemediationAI

Upgrade to patched versions immediately: GitLab EE 18.8.7 or later for the 18.8 branch, 18.9.3 or later for the 18.9 branch, or 18.10.1 or later for the 18.10 branch. Follow the vendor patch release notes at https://about.gitlab.com/releases/2026/03/25/patch-release-gitlab-18-10-1-released/ for upgrade procedures and any breaking changes. If immediate patching is not feasible, implement a compensating control by auditing and restricting the Planner role assignment to users who genuinely require planning features only, and ensure that security administrators monitor group security configuration access logs for unauthorized viewing patterns. Additionally, enforce network-level access controls to limit who can authenticate to the GitLab instance, and consider implementing an API gateway to restrict access to group security endpoints based on user roles.