CVE-2025-10903
Received Received - Intake

Denial of Service in GitLab EE via SCIM Provisioning

Vulnerability report for CVE-2025-10903, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-26

Last updated on: 2026-08-26

Assigner: GitLab Inc.

Description

GitLab has remediated an issue in GitLab EE affecting all versions from 11.10 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user could have caused denial of service, due to an unbounded loop triggered by specially crafted input in the SCIM user provisioning feature.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-26
Last Modified
2026-08-26
Generated
2026-08-26
AI Q&A
2026-08-26
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
gitlab gitlab_ee From 11.10 (inc) to 19.1.7 (exc)
gitlab gitlab_ee From 19.2 (inc) to 19.2.5 (exc)
gitlab gitlab_ee From 19.3 (inc) to 19.3.1 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-835 The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in GitLab EE allows an authenticated user to cause a denial of service through an unbounded loop triggered by specially crafted input in the SCIM user provisioning feature. It affects versions from 11.10 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1.

Detection Guidance

This vulnerability is specific to GitLab EE versions 11.10 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1. To detect it, check your GitLab EE version using the command: gitlab-rake gitlab:env:info. If your version falls within the affected range, the system is vulnerable.

Impact Analysis

An attacker could exploit this to disrupt GitLab services, making them unavailable to users. This could lead to downtime, loss of productivity, and potential data access issues if services are interrupted.

Mitigation Strategies

Upgrade GitLab EE to a patched version: 19.1.7, 19.2.5, or 19.3.1 or later. After upgrading, verify the fix by running gitlab-rake gitlab:env:info again to confirm the version is no longer vulnerable.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-10903. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart