CVE-2026-92628 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') in GitLab

Low 3.1 Published Updated

A race condition in GitLab's MCP search tool allows attackers to view search results belonging to other users due to improper synchronization of shared state.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-92628?

CVE-2026-92628 is a low-severity vulnerability in Gitlab Gitlab, published on 23 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

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.

Weakness: CWE-362

Which versions are affected by CVE-2026-92628?

1 open source package ship an affected version, including gitlab. It affects 1 product.

PackageAffectedFixed in
gitlab BitnamiFrom 18.6.019.2.7, 19.3.3, 19.4.1

Products include Gitlab Gitlab.

How do I fix CVE-2026-92628?

Upgrade gitlab to a fixed version for your release line: 19.2.7, 19.3.3 or 19.4.1.

Is CVE-2026-92628 being exploited?

There is no known exploitation of CVE-2026-92628 in the wild and no public exploit code.

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2026-92628, GHSA-vp7f-562j-4qgr, MINI-2956-7m32-frr2, MINI-2jrx-85pf-wg4v, MINI-2rg5-8876-fxwq, MINI-52fm-5359-47fq and 35 more.

Is CVE-2026-92628 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free