<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/gitlab-critical-patch-release-19-4-1-19-3-3-19-2-7-rdpef3qur" -->

---
title: GitLab Critical Patch Release: 19.4.1, 19.3.3, 19.2.7
description: GitLab released critical patch versions 19.4.1, 19.3.3, and 19.2.7 for Community Edition and Enterprise Edition on September 23, 2026, fixing 11 security...
canonical: https://daily.dev/posts/gitlab-critical-patch-release-19-4-1-19-3-3-19-2-7-rdpef3qur
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: GitLab Critical Patch Release: 19.4.1, 19.3.3, 19.2.7 | daily.dev
og:description: GitLab released critical patch versions 19.4.1, 19.3.3, and 19.2.7 for Community Edition and Enterprise Edition on September 23, 2026, fixing 11 security...
og:url: https://daily.dev/posts/gitlab-critical-patch-release-19-4-1-19-3-3-19-2-7-rdpef3qur
og:image: https://api.daily.dev/og/posts/Rdpef3Qur.png
og:image:alt: GitLab Critical Patch Release: 19.4.1, 19.3.3, 19.2.7
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# GitLab Critical Patch Release: 19.4.1, 19.3.3, 19.2.7

**[GitLab](https://daily.dev/sources/gitlab)** · 9 min read · 0 upvotes · 0 comments

## Summary

GitLab released critical patch versions 19.4.1, 19.3.3, and 19.2.7 for Community Edition and Enterprise Edition on September 23, 2026, fixing 11 security vulnerabilities. The most severe are two CVSS 9.9 remote code execution issues in the CI/CD regular expression parser and compiler (CVE-2026-89078 and CVE-2026-93577), plus an XSS flaw in the merge request diff viewer (CVSS 8.7) and several lower-severity authorization issues affecting Duo AI, MCP tokens, GraphQL APIs, and Direct Transfer imports. GitLab.com is already patched; self-managed instances are urged to upgrade immediately. The release also includes numerous bug fixes and dependency bumps (PostgreSQL 17.11, Consul 1.22.7). Single-node instances will experience downtime during the upgrade due to required database migrations, while multi-node instances can use zero-downtime procedures.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-1-released>

## Questions this post answers

### What vulnerabilities does GitLab 19.4.1 fix and should I upgrade immediately?

GitLab 19.4.1, along with 19.3.3 and 19.2.7, fixes 11 security issues including two critical CVSS 9.9 remote code execution flaws (CVE-2026-89078 and CVE-2026-93577) caused by a double free and integer overflow in the regular expression parser and compiler used for CI/CD configuration. An 8.7 CVSS cross-site scripting flaw in the merge request diff viewer is also patched. Self-managed installations should upgrade immediately.

_daily.dev surfaces critical GitLab security releases so self-managed instances don't fall behind on patching._

### Will upgrading GitLab to 19.3.3 or 19.2.7 cause downtime?

It depends on the deployment topology: single-node GitLab instances will experience downtime during the upgrade because required database migrations must complete before GitLab can start, while multi-node instances can avoid downtime by following GitLab's zero-downtime upgrade procedures. Versions 19.3.3 and 19.2.7 also include post-deploy migrations that run after the upgrade completes.

_Teams planning a GitLab upgrade window can track downtime implications like these via daily.dev._

### What is the GitLab MCP API scope enforcement vulnerability CVE-2026-92874?

CVE-2026-92874 is an incorrect authorization issue in GitLab's MCP API scope enforcement that could let an authenticated user holding an MCP-scoped token perform actions beyond that token's intended scope, due to improper authorization checks. It carries a CVSS score of 5.4 and affects GitLab CE/EE versions from 18.3 up to 19.2.7, 19.3.3, and 19.4.1.

_Developers securing MCP-integrated tooling can follow disclosures like this one on daily.dev._

## Similar posts on daily.dev

- [GitLab Patch Release: 19.0.1, 18.11.4, 18.10.7](https://daily.dev/posts/gitlab-patch-release-19-0-1-18-11-4-18-10-7-zr6cdslky) · GitLab · 0 upvotes · 0 comments
- [Over 1,000 GitLab servers vulnerable to ongoing RCE attacks](https://daily.dev/posts/over-1-000-gitlab-servers-vulnerable-to-ongoing-rce-attacks-dsbgbwvkf) · BleepingComputer · 3 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#devops](https://daily.dev/tags/devops), [#cicd](https://daily.dev/tags/cicd), [#gitlab](https://daily.dev/tags/gitlab)

[View this post on daily.dev](https://daily.dev/posts/gitlab-critical-patch-release-19-4-1-19-3-3-19-2-7-rdpef3qur)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"GitLab Critical Patch Release: 19.4.1, 19.3.3, 19.2.7","url":"https://daily.dev/posts/gitlab-critical-patch-release-19-4-1-19-3-3-19-2-7-rdpef3qur","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/gitlab-critical-patch-release-19-4-1-19-3-3-19-2-7-rdpef3qur"},"datePublished":"2026-09-23T22:15:47.191Z","dateModified":"2026-09-23T22:16:12.919Z","description":"GitLab released critical patch versions 19.4.1, 19.3.3, and 19.2.7 for Community Edition and Enterprise Edition on September 23, 2026, fixing 11 security...","image":"https://media.daily.dev/image/upload/s--58gMhC4P--/f_auto/v1722860399/public/Placeholder%2012","thumbnailUrl":"https://media.daily.dev/image/upload/s--58gMhC4P--/f_auto/v1722860399/public/Placeholder%2012","isAccessibleForFree":true,"articleSection":"GitLab","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"GitLab","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/3720ce340ca4435daef529abbf361b69","url":"https://daily.dev/sources/gitlab"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/gitlab-critical-patch-release-19-4-1-19-3-3-19-2-7-rdpef3qur","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,devops,cicd,gitlab","timeRequired":"PT9M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"GitLab","item":"https://daily.dev/sources/gitlab"},{"@type":"ListItem","position":3,"name":"GitLab Critical Patch Release: 19.4.1, 19.3.3, 19.2.7"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/gitlab-critical-patch-release-19-4-1-19-3-3-19-2-7-rdpef3qur#faq","mainEntity":[{"@type":"Question","name":"What vulnerabilities does GitLab 19.4.1 fix and should I upgrade immediately?","acceptedAnswer":{"@type":"Answer","text":"GitLab 19.4.1, along with 19.3.3 and 19.2.7, fixes 11 security issues including two critical CVSS 9.9 remote code execution flaws (CVE-2026-89078 and CVE-2026-93577) caused by a double free and integer overflow in the regular expression parser and compiler used for CI/CD configuration. An 8.7 CVSS cross-site scripting flaw in the merge request diff viewer is also patched. Self-managed installations should upgrade immediately. daily.dev surfaces critical GitLab security releases so self-managed instances don't fall behind on patching."}},{"@type":"Question","name":"Will upgrading GitLab to 19.3.3 or 19.2.7 cause downtime?","acceptedAnswer":{"@type":"Answer","text":"It depends on the deployment topology: single-node GitLab instances will experience downtime during the upgrade because required database migrations must complete before GitLab can start, while multi-node instances can avoid downtime by following GitLab's zero-downtime upgrade procedures. Versions 19.3.3 and 19.2.7 also include post-deploy migrations that run after the upgrade completes. Teams planning a GitLab upgrade window can track downtime implications like these via daily.dev."}},{"@type":"Question","name":"What is the GitLab MCP API scope enforcement vulnerability CVE-2026-92874?","acceptedAnswer":{"@type":"Answer","text":"CVE-2026-92874 is an incorrect authorization issue in GitLab's MCP API scope enforcement that could let an authenticated user holding an MCP-scoped token perform actions beyond that token's intended scope, due to improper authorization checks. It carries a CVSS score of 5.4 and affects GitLab CE/EE versions from 18.3 up to 19.2.7, 19.3.3, and 19.4.1. Developers securing MCP-integrated tooling can follow disclosures like this one on daily.dev."}}]}
```

