Skip to main content
Mallory
MediumVulnerability

CVE-2026-123142: Incorrect Authorization in GitLab MCP Server

Published Nov 17, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days3 mentions · peak 2 in a dayToday
CVSS4.3Medium · v3.1
EPSS0.17%6th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-123142CWE-863 · Incorrect Authorization

CVE-2026-123142 is an incorrect authorization vulnerability in the GitLab CE/EE MCP server. Under certain conditions, an authenticated user holding an MCP-scoped OAuth token can perform unauthorized state changes on issues and merge requests, including approving and merging merge requests. Affected versions are 18.4 through versions before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises issue and merge request integrity by permitting state changes outside the authorization boundaries intended for MCP-scoped OAuth tokens. Unauthorized approval and merging can undermine code-review and merge controls. The published CVSS v3.0 score is 4.3, with low integrity impact and no confidentiality or availability impact.

Mitigation

If you can’t patch tonight, do this now.

No temporary workaround is specified.

Remediation

Patch, then assume compromise.

Upgrade affected self-managed GitLab CE/EE installations to version 19.3.9, 19.4.8, or 19.5.6, as appropriate for the release branch. GitLab.com is already patched, and GitLab Dedicated customers require no action.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-123142 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-123142 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-123142?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-123142.
Is there a patch for CVE-2026-123142?
Upgrade affected self-managed GitLab CE/EE installations to version 19.3.9, 19.4.8, or 19.5.6, as appropriate for the release branch. GitLab.com is already patched, and GitLab Dedicated customers require no action.
How severe is CVE-2026-123142?
CVE-2026-123142 has a CVSS v3.1 score of 4.3 (Medium) and an EPSS score of 0.17% (6th percentile) as of Nov 17, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.