GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.3 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 that under… (CVE-2026-92874)
A vulnerability in GitLab CE/EE versions from 18.3 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 allows an authenticated user with an MCP-scoped token to perform actions beyond the intended scope due to improper authorization checks. This issue has been remediated in versions 19.2.7, 19.3.3, and 19.4.1. The vulnerability has a medium severity rating with a CVSS score of 5.4.
AI Analysis
Technical Summary
CVE-2026-92874 is an authorization bypass vulnerability in GitLab Community Edition and Enterprise Edition affecting versions from 18.3 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. Under certain conditions, an authenticated user possessing an MCP-scoped token could perform actions beyond the intended scope of that token due to improper authorization checks. This could lead to limited confidentiality and integrity impacts but no availability impact. The issue has been fixed in the specified patched versions.
Potential Impact
An authenticated user with an MCP-scoped token could execute unauthorized actions beyond their intended permissions, potentially leading to limited confidentiality and integrity breaches within the GitLab environment. There is no indication of availability impact or active exploitation in the wild.
Mitigation Recommendations
Upgrade GitLab CE/EE to versions 19.2.7, 19.3.3, or 19.4.1 or later to apply the official fix. Since the vendor has remediated the issue in these versions, applying these updates will mitigate the vulnerability.
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.3 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 that under… (CVE-2026-92874)
Description
A vulnerability in GitLab CE/EE versions from 18.3 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 allows an authenticated user with an MCP-scoped token to perform actions beyond the intended scope due to improper authorization checks. This issue has been remediated in versions 19.2.7, 19.3.3, and 19.4.1. The vulnerability has a medium severity rating with a CVSS score of 5.4.
CVSS v3.1
Score 5.4medium
Affected software
pkg:gem/gitlab-org/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-92874 is an authorization bypass vulnerability in GitLab Community Edition and Enterprise Edition affecting versions from 18.3 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. Under certain conditions, an authenticated user possessing an MCP-scoped token could perform actions beyond the intended scope of that token due to improper authorization checks. This could lead to limited confidentiality and integrity impacts but no availability impact. The issue has been fixed in the specified patched versions.
Potential Impact
An authenticated user with an MCP-scoped token could execute unauthorized actions beyond their intended permissions, potentially leading to limited confidentiality and integrity breaches within the GitLab environment. There is no indication of availability impact or active exploitation in the wild.
Mitigation Recommendations
Upgrade GitLab CE/EE to versions 19.2.7, 19.3.3, or 19.4.1 or later to apply the official fix. Since the vendor has remediated the issue in these versions, applying these updates will mitigate the vulnerability.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-c3rm-3hqr-4qwm
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-92874"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6ab4be1df7a7c54106eee6bf
Added to database: 09/24/2026, 06:07:25 UTC
Last enriched: 09/24/2026, 06:16:54 UTC
Last updated: 09/25/2026, 03:03:52 UTC
Views: 7
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.