CVE-2026-92628: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') in GitLab
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.6 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 that under a race condition, the MCP search tool's shared state handling could have caused search results to be returned under an incorrect user context.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 19.2.7 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 19.3.3 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 19.4.1
Event History
Frequently Asked Questions
Which GitLab versions contain the fixes?
The issue is fixed in GitLab 19.2.7, 19.3.3, and 19.4.1. Versions from 18.6 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 are affected.
What level of access and conditions are required for exploitation?
The provided CVSS vector indicates network reachability, low attacker privileges, no user interaction, and high attack complexity. Exploitation depends on triggering the relevant race condition in the MCP search tool's shared-state handling.