Menu

Star on GitHub · 3.2k

CVE-2025-10871

3.8 · LOW

An issue has been discovered in GitLab EE affecting all versions from 16.6 before 18.2.7, 18.3 before 18.3.3, and 18.4 before 18.4.1.

Published Sep 26, 2025CWE-862EPSS 0.38%

Overview

CVE-2025-10871 is a low-severity vulnerability. It was published on September 26, 2025 and has a CVSS 3.1 base score of 3.8 (LOW).

This vulnerability has a CVSS 3.1 base score of 3.8, rated LOW. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical description

An issue has been discovered in GitLab EE affecting all versions from 16.6 before 18.2.7, 18.3 before 18.3.3, and 18.4 before 18.4.1. Project Maintainers can exploit a vulnerability where they can assign custom roles to users with permissions exceeding their own, effectively granting themselves elevated privileges.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-10871?

CVE-2025-10871 is a low-severity vulnerability. It was published on September 26, 2025 and has a CVSS 3.1 base score of 3.8 (LOW).

How severe is CVE-2025-10871?

This vulnerability has a CVSS 3.1 base score of 3.8, rated LOW. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2025-10871?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-10871?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-10871 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2025

View all