Skip to content
Fencer Vulns
low 3.1

CVE-2026-92628 json

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') in GitLab

published 2026-09-23 46 d ago modified 2026-10-01 38 d ago also BIT-gitlab-2026-92628 , EUVD-2026-85731

cvss
3.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 3%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami gitlab 19.2.7, 19.3.3, 19.4.1
  • GitLab GitLab 19.2.7, 19.3.3, 19.4.1

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
45 d ago

Exploit prediction

0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
OSV 3.1 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
bitnami gitlab
>=18.6.0, <19.2.7
>=19.3.0, <19.3.3
>=19.4.0, <19.4.1
19.2.7
19.3.3
19.4.1

Affected products

  • GitLab GitLab

Classification

Weakness
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.