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… (CVE-2026-92530)
A vulnerability in GitLab CE/EE versions from 19.1 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 could allow an authenticated user to spoof merge request authorship and attribute content to arbitrary existing users due to improper reliance on ephemeral cache state during Direct Transfer imports. This issue has been remediated by GitLab.
AI Analysis
Technical Summary
CVE-2026-92530 affects GitLab Community and Enterprise Editions in versions from 19.1 up to but not including 19.2.7, 19.3 up to but not including 19.3.3, and 19.4 up to but not including 19.4.1. The vulnerability arises from improper reliance on ephemeral cache state during Direct Transfer imports, which under certain conditions could allow an authenticated user to spoof merge request authorship and attribute content to arbitrary existing users on the target instance. This could lead to misinformation about code authorship within the affected GitLab instances.
Potential Impact
The impact is limited to the integrity of merge request authorship attribution, potentially misleading users about who authored specific content. There is no impact on confidentiality or availability. The CVSS score is 4.3 (medium severity), reflecting limited impact with no confidentiality or availability loss.
Mitigation Recommendations
GitLab has remediated this issue in versions 19.2.7, 19.3.3, and 19.4.1 and later. Users should upgrade to these fixed versions or later to mitigate this vulnerability. No other mitigation actions are indicated.
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… (CVE-2026-92530)
Description
A vulnerability in GitLab CE/EE versions from 19.1 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 could allow an authenticated user to spoof merge request authorship and attribute content to arbitrary existing users due to improper reliance on ephemeral cache state during Direct Transfer imports. This issue has been remediated by GitLab.
CVSS v3.1
Score 4.3medium
Affected software
pkg:gem/gitlabRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-92530 affects GitLab Community and Enterprise Editions in versions from 19.1 up to but not including 19.2.7, 19.3 up to but not including 19.3.3, and 19.4 up to but not including 19.4.1. The vulnerability arises from improper reliance on ephemeral cache state during Direct Transfer imports, which under certain conditions could allow an authenticated user to spoof merge request authorship and attribute content to arbitrary existing users on the target instance. This could lead to misinformation about code authorship within the affected GitLab instances.
Potential Impact
The impact is limited to the integrity of merge request authorship attribution, potentially misleading users about who authored specific content. There is no impact on confidentiality or availability. The CVSS score is 4.3 (medium severity), reflecting limited impact with no confidentiality or availability loss.
Mitigation Recommendations
GitLab has remediated this issue in versions 19.2.7, 19.3.3, and 19.4.1 and later. Users should upgrade to these fixed versions or later to mitigate this vulnerability. No other mitigation actions are indicated.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-wr3r-jhmc-f6jw
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-92530"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6ab4be1df7a7c54106eee6b6
Added to database: 09/24/2026, 06:07:25 UTC
Last enriched: 09/24/2026, 06:16:44 UTC
Last updated: 09/24/2026, 15:45:50 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.