# GitLab GitLab Patch Release: 19.0.1, 18.11.4, 18.10.7

- Product: GitLab (https://whatsnew.fyi/product/gitlab)
- Vendor: GitLab
- Date: 2026-05-27
- Original notes: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-0-1-released/
- Permalink: https://whatsnew.fyi/product/gitlab/releases/2026-05-27-gitlab-patch-release-19.0.1-18.11.4-18.10.7

What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog.

Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'.

---

On May 27, 2026, we released versions 19.0.1, 18.11.4, 18.10.7 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly r…

- **security** — Remediated an Improper Access Control issue in Duo AI workflow runners that could have allowed an authenticated user to cause specific Duo AI workflows to run under another user's identity
- **security** — Remediated a Denial of Service issue in Wiki that could have allowed an authenticated user to cause denial of service due to insufficient validation
- **security** — Remediated an Incorrect Authorization issue in GraphQL WorkItem API that could have allowed an unauthorized user to enumerate private projects due to incorrect authorization checks
- **security** — Remediated an Improper Authorization issue in Duo Workflows API that could have allowed an authenticated user with developer-role permissions to bypass flow restrictions when foundational flows were enabled at the group level
- **security** — Remediated a Missing Authorization issue in Operations that could have allowed an authenticated user with developer-role permissions to access sensitive deployment data on projects
- **security** — Remediated an Incorrect Name Resolution issue in Pipelines that could have allowed an authenticated user to access CI data from a different ref type than intended
- **security** — Remediated an Incorrect Authorization issue in certain authentication endpoints that could have allowed a blocked Project Access Token to continue accessing private resources

Help us learn about your current experience with the documentation. Take the survey.
#### GitLab Patch Release: 19.0.1, 18.11.4, 18.10.7
On May 27, 2026, we released versions 19.0.1, 18.11.4, 18.10.7 for GitLab Community Edition (CE) and Enterprise Edition (EE).
These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action.
GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch releases: scheduled releases and ad-hoc critical patches for high-severity vulnerabilities. Scheduled releases are released twice a month on the second and fourth Wednesdays. For more information, please visit our releases handbook and security FAQ. You can see all of GitLab release blog posts here.
For security fixes, the issues detailing each vulnerability are made public on our issue tracker 30 days after the release in which they were patched.
We are committed to ensuring that all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. To maintain good security hygiene, it is highly recommended that all customers upgrade to the latest patch release for their supported version. You can read more best practices in securing your GitLab instance in our blog post.
###### Recommended Action
We strongly recommend that all installations running a version affected by the issues described below are upgraded to the latest version as soon as possible.
When no specific deployment type (omnibus, source code, helm chart, etc.) of a product is mentioned, it means all types are affected.
##### Security fixes
###### Table of security fixes
TitleSeverity
Improper Access Control issue in Duo AI workflow runners impacts GitLab EEHigh
Denial of Service issue in Wiki impacts GitLab CE/EEMedium
Incorrect Authorization issue in GraphQL WorkItem API impacts GitLab CE/EEMedium
Improper Authorization issue in Duo Workflows API impacts GitLab EEMedium
Missing Authorization issue in Operations impacts GitLab EEMedium
Incorrect Name Resolution issue in Pipelines impacts GitLab CE/EEMedium
Incorrect Authorization issue in certain authentication endpoints impacts GitLab CE/EEMedium
###### CVE-2026-4868 - Improper Access Control issue in Duo AI workflow runners impacts GitLab EE
GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user to cause specific Duo AI workflows to run under another user’s identity due to improper user identity resolution when triggering Duo AI workflow runners.
Impacted Versions: GitLab EE: all versions from 18.8 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1CVSS 8.2 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N)
Thanks ahacker1 for reporting this vulnerability through our HackerOne bug bounty program
###### CVE-2026-1402 - Denial of Service issue in Wiki impacts GitLab CE/EE
GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to cause denial of service due to insufficient validation.
Impacted Versions: GitLab CE/EE: all versions from 17.1 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Thanks a92847865 for reporting this vulnerability through our HackerOne bug bounty program
###### CVE-2026-6713 - Incorrect Authorization issue in GraphQL WorkItem API impacts GitLab CE/EE
GitLab has remediated an issue that under certain conditions could have allowed an unauthorized user to enumerate private projects due to incorrect authorization checks.
Impacted Versions: GitLab CE/EE: all versions from 18.2 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1CVSS 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)
Thanks pollito for reporting this vulnerability through our Hacke

_[Truncated at 4000 characters — full notes: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-0-1-released/]_