GitLab patches 37 flaws including XSS bug CVE-2026-105739 in 19.5.6 release
By aminah
·17 Nov 2026
·3 min read

GitLab has released patch versions 19.5.6, 19.4.8 and 19.3.9, fixing 37 security vulnerabilities across its Community and Enterprise editions, including four high-severity flaws that administrators of self-managed installations should patch now. GitLab.com has already been patched, and GitLab Dedicated customers need take no action.
The most serious flaws are two cross-site scripting (XSS) bugs, both rated 8.7 out of 10. CVE-2026-105739 affects wiki pages: an authenticated user could execute arbitrary JavaScript in the browser of anyone viewing a wiki page, because user input was not properly sanitised. It affects all versions from 17.2. The second, CVE-2026-108153, is the same class of flaw in GitLab's Error Tracking pages, affecting versions from 16.1. In both cases, a successful attack could lead to session hijacking and account takeover, including of administrator accounts.
## CI/CD variables exposed by race condition
The third high-severity flaw, CVE-2026-18241, rated 8.2, is a race condition in pipeline job authorisation. Under certain conditions, an authenticated user could access protected CI/CD variables and resources that should have been out of reach. The flaw affects versions from 9.3, making it the longest-lived of the four.
The fourth, CVE-2026-97187, rated 7.6, affects GitLab workspaces connected to Kubernetes clusters through the GitLab agent. Incorrect authorisation checks could have allowed an authenticated user to read Kubernetes Secrets from other namespaces. It affects versions from 17.6.
## AI features also patched
The release also fixes flaws in GitLab's AI surface. CVE-2026-123142, rated 4.3, allowed an authenticated user holding an MCP-scoped OAuth token to change the state of issues and merge requests, including approving and merging them, beyond what the token permitted. Three further authorisation flaws in the Duo Agent Platform, each rated 4.3, were also fixed, along with a medium-severity path traversal flaw in GitLab Pages, CVE-2026-11768. In total the release fixes four high-severity, 24 medium-severity and nine low-severity issues.
GitLab says it has seen no reports of these flaws being exploited, and no public proof-of-concept code has been confirmed. None of the four high-severity flaws is listed in CISA's Known Exploited Vulnerabilities catalogue. Full technical details of each issue will be published 90 days after the release, which is a further reason to patch before that information becomes public.
## What administrators should do
Self-managed GitLab administrators should upgrade to 19.5.6, 19.4.8 or 19.3.9, depending on their current branch, as soon as possible. GitLab says the releases introduce no new database migrations, although the standard Omnibus upgrade still stops and restarts services. Organisations that cannot patch immediately should review who has access to wiki pages, Error Tracking pages and CI/CD pipelines, and check for unusual activity in those areas.
The release follows earlier emergency patches this autumn, including version 19.5.4, which fixed a heap overflow flaw in Gitaly, CVE-2026-105437. Security researchers have noted that GitLab's CI/CD authorisation and data-exposure fixes have formed a running theme in recent releases.
## Frequently asked questions
**Which GitLab versions are affected?** All versions before 19.3.9, 19.4.8 or 19.5.6, depending on the branch, with the starting version varying by flaw — as far back as version 9.3 for the CI/CD race condition.
**Is GitLab.com affected?** No. GitLab says GitLab.com has already been patched and GitLab Dedicated customers need take no action.
**Have the flaws been exploited?** GitLab reports no exploitation, and no public proof-of-concept has been confirmed. The flaws are not listed in CISA's Known Exploited Vulnerabilities catalogue.
Sources: [GitLab patch release 19.5.6](https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-6-released/) and [SecurityOnline](https://securityonline.info/gitlab-patch-release-19-5-6/).
Source
SecurityOnline — https://securityonline.info/gitlab-patch-release-19-5-6/