Widely used GitLab MCP Server; critical auth bypass enabling unauthenticated RPC with operator PAT; high exposure until patch.
CVE-2026-44895
Auth bypass in GitLab MCP Server allows unauthenticated RPC via HTTP.
Is CVE-2026-44895 being exploited?
Not confirmed. CVE-2026-44895 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.39% probability of exploitation in the next 30 days.
How severe is CVE-2026-44895?
CVE-2026-44895 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-44895?
Yes. A fix has been recorded for CVE-2026-44895. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-44895 affect?
CVE-2026-44895 affects GitLab MCP Server (pre-0.6.0). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-44895?
Upgrade to 0.6.0+; revoke/rotate tokens; apply network access controls.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker can perform privileged RPC actions using operator PAT without credential checks; cross-origin surface exposed via wildcard CORS.
Immediate action required
- affected< 0.6.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.