GitLab CE/EE 18.619.4.1 Race Cond in MCP Search
CVE-2026-92628 Published on September 23, 2026
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.
Vulnerability Analysis
CVE-2026-92628 is exploitable with network access, and requires small amount of user privileges. This vulnerability is consided to have a high level of attack complexity. The potential impact of an exploit of this vulnerability is considered to have a small impact on confidentiality, a small impact on integrity and availability.
Weakness Type
What is a Race Condition Vulnerability?
The program contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently.
CVE-2026-92628 has been classified to as a Race Condition vulnerability or weakness.
Products Associated with CVE-2026-92628
Want to know whenever a new CVE is published for GitLab? stack.watch will email you.
Affected Versions
GitLab:- Version 18.6 and below 19.2.7 is affected.
- Version 19.3 and below 19.3.3 is affected.
- Version 19.4 and below 19.4.1 is affected.