CVE-2026-92530: Use of Less Trusted Source in GitLab
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.1 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 that under certain conditions could have allowed an authenticated user to spoof merge request authorship and attribute content to arbitrary existing users on the target instance due to improper reliance on ephemeral cache state during Direct Transfer imports.
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
Who can exploit this issue?
An attacker needs to be an authenticated user on the target GitLab instance. The issue affects Direct Transfer imports under certain conditions and could allow spoofing merge request authorship for arbitrary existing users on that instance.
Which GitLab versions need remediation?
Affected versions are GitLab CE/EE 19.1 through before 19.2.7, 19.3 through before 19.3.3, and 19.4 through before 19.4.1. Upgrade to 19.2.7, 19.3.3, 19.4.1, or a later version in the applicable release line.
What is the security impact of successful exploitation?
Successful exploitation can falsely attribute merge-request content to an arbitrary existing user. The provided vector indicates integrity impact only; no confidentiality or availability impact is specified.