CVE-2026-92874 GitLab CVE debrief

Who should care

GitLab administrators and security teams should assess exposure and apply necessary patches or mitigations to prevent unintended actions by authenticated users with MCP-scoped tokens.

Why it matters

Defenders should care about CVE-2026-92874 because it allows authenticated users with MCP-scoped tokens to perform unintended actions in GitLab instances, potentially leading to security risks if not properly addressed.

• Verification of GitLab instance versions and MCP-scoped token usage is necessary.
• Restricting and monitoring MCP-scoped token actions can help mitigate potential risks.
• Applying patches or mitigations for affected versions is crucial to prevent exploitation.

Technical summary

The vulnerability allows an authenticated user with an MCP-scoped token to perform actions beyond the intended scope due to improper authorization checks 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. This issue could have allowed unintended actions by authenticated users with MCP-scoped tokens, potentially leading to security risks if not properly addressed. Defenders should prioritize verifying exposure in their GitLab instances, especially those with MCP-scoped tokens in use, and apply patches or mitigations as needed.

Defensive priority

Defenders should prioritize verifying exposure in their GitLab instances, especially those with MCP-scoped tokens in use, and apply patches or mitigations as needed.

Recommended defensive actions

• Verify GitLab instance versions and apply patches or mitigations for affected versions.
• Review and restrict the use of MCP-scoped tokens.
• Monitor for unusual activity related to authenticated user actions.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and NVD entry provide details on the affected versions and the nature of the vulnerability. Vendor advisories and issue tracking links are available for further information. The issue is remediated in versions 19.2.7, 19.3.3, and 19.4.1. Defenders should verify exposure in their GitLab instances, especially those with MCP-scoped tokens in use, and apply patches or mitigations as needed. The CVE Program and NVD provide official records and assessments of the vulnerability.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.