# CVE-2026-92874: GitLab CE/EE incorrect authorization in MCP API scope enforcement

Source: https://junglewise.ai/threats/cve-2026-92874-gitlab-has-remediated-an-issue-in-gitlab-ce-ee-affecting-all  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-24. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-92874 · Severity: medium · CVSS 5.4 · Published 2026-09-24

GitLab is a DevOps platform that manages source code repositories and CI/CD pipelines for development teams. An authentication vulnerability in GitLab allows users with limited-permission tokens (MCP-scoped) to perform actions beyond their authorized scope. An attacker with a restricted token could access or modify resources they should not have permission to use, potentially exposing sensitive project data or making unauthorized changes to pipelines and code.

Technologies: [GitLab EE](https://junglewise.ai/threats/technologies/ee), [GitLab CE](https://junglewise.ai/threats/technologies/gitlab-ce). Vendors: [GitLab](https://junglewise.ai/threats/vendors/gitlab).

## Quick answers

**Is CVE-2026-92874 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-92874 being exploited in the wild.

**How severe is CVE-2026-92874?** Medium severity, with a CVSS score of 5.4, published 24 September 2026.

**Which products and versions are affected?** GitLab EE 18.3 to 19.2.6, 19.3.0 to 19.3.2, 19.4.0; GitLab CE 18.3 to 19.2.6, 19.3.0 to 19.3.2, 19.4.0.

**Is there a fix for CVE-2026-92874?** A patch was published on 2026-09-23: Patches released in GitLab 19.4.1, 19.3.3, and 19.2.7 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-92874 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-92874?** Check whether you run GitLab EE or GitLab CE at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is an improper authorization check in GitLab's MCP API token scope enforcement. An authenticated user possessing an MCP-scoped token can bypass scope restrictions through network requests with no additional user interaction required. The flaw allows privilege escalation within the API, enabling actions that should be denied based on token scope restrictions, affecting versions 18.3 through 19.4.0.

## Affected products

- GitLab CE 18.3 to 19.2.6, 19.3.0 to 19.3.2, 19.4.0
- GitLab EE 18.3 to 19.2.6, 19.3.0 to 19.3.2, 19.4.0

## Timeline

- 2026-09-24: disclosed
- 2026-09-23: patched: Patches released in GitLab 19.4.1, 19.3.3, and 19.2.7

## References

- [https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-1-released/](https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-1-released/)
- [https://gitlab.com/gitlab-org/gitlab/-/work_items/618614](https://gitlab.com/gitlab-org/gitlab/-/work_items/618614)

## Related threats

- [GitLab authorization bypass in group milestones API](https://junglewise.ai/threats/cve-2026-13319-gitlab-has-remediated-an-issue-in-gitlab-ce-ee-affecting-all)
- [GitLab CE/EE improper access control in GraphQL work item email field](https://junglewise.ai/threats/cve-2026-12664-gitlab-has-remediated-an-issue-in-gitlab-ce-ee-affecting-all)
- [GitLab integer overflow in regular expression compiler](https://junglewise.ai/threats/cve-2026-110264-an-issue-has-been-discovered-in-gitlab-ce-ee-affecting-all)
- [GitLab CE/EE integer overflow in CI/CD regular expression compiler](https://junglewise.ai/threats/cve-2026-97229-gitlab-has-remediated-an-issue-in-gitlab-ce-ee-affecting-all)
- [GitLab open redirect in Kubernetes proxy](https://junglewise.ai/threats/cve-2026-7767-gitlab-has-remediated-an-issue-in-gitlab-ce-ee-affecting-all)