# GitLab GitLab Patch Release: 19.1.2, 19.0.4, 18.11.7

- Product: GitLab (https://whatsnew.fyi/product/gitlab)
- Vendor: GitLab
- Date: 2026-07-08
- Original notes: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-1-2-released/
- Permalink: https://whatsnew.fyi/product/gitlab/releases/2026-07-08-gitlab-patch-release-19.1.2-19.0.4-18.11.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 July 8, 2026, we released versions 19.1.2, 19.0.4, 18.11.7 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly re…

- **security** — Fixed Cross-site Scripting issue in vulnerability evidence table renderer in GitLab EE
- **security** — Fixed HTML Injection in wiki markup rendering in GitLab CE/EE
- **security** — Fixed Insufficiently Protected Credentials issue in repository mirroring in GitLab EE
- **security** — Fixed Improper Access Control issue in work items in GitLab EE
- **security** — Fixed Missing Authorization issue in commit discussion display in GitLab CE/EE
- **security** — Fixed Ambiguity Reference issue in a tag or branch in GitLab CE/EE
- **security** — Fixed Incorrect Authorization issue in group-level settings in GitLab EE
- **security** — Fixed Incorrect Authorization issue in compliance violation management in GitLab EE

Help us learn about your current experience with the documentation. Take the survey.
#### GitLab Patch Release: 19.1.2, 19.0.4, 18.11.7
On July 8, 2026, we released versions 19.1.2, 19.0.4, 18.11.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 90 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
Cross-site Scripting issue in vulnerability evidence table renderer impacts GitLab EEHigh
HTML Injection in wiki markup rendering impacts GitLab CE/EEHigh
Insufficiently Protected Credentials issue in repository mirroring impacts GitLab EEMedium
Improper Access Control issue in work items impacts GitLab EEMedium
Missing Authorization issue in commit discussion display impacts GitLab CE/EEMedium
Ambiguity Reference issue in a tag or branch impacts GitLab CE/EELow
Incorrect Authorization issue in group-level settings impacts GitLab EELow
Incorrect Authorization issue in compliance violation management impacts GitLab EELow
###### CVE-2026-6896 - Cross-site Scripting issue in vulnerability evidence table renderer impacts GitLab EE
GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with developer-role permissions to execute arbitrary scripts in another user’s browser session due to improper sanitization of user-supplied input.
Impacted Versions: GitLab EE: all versions from 13.11 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2CVSS 8.7 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N)
Thanks yvvdwf for reporting this vulnerability through our HackerOne bug bounty program
###### CVE-2026-13320 - HTML Injection in wiki markup rendering impacts GitLab CE/EE
GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to execute arbitrary scripts in another user’s browser session due to improper sanitization of user-supplied input.
Impacted Versions: GitLab CE/EE: all versions from 15.7 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2CVSS 7.3 (CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:N)
Thanks youzslan and a_m_a_m for reporting this vulnerability through our HackerOne bug bounty program
###### CVE-2026-11827 - Insufficiently Protected Credentials issue in repository mirroring impacts GitLab EE
GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with maintainer-role permissions to obtain another user’s stored credentials due to improper authorization controls.

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