GitLab 19.5.6 Patches 37 Vulnerabilities, Including Two CVSS 8.7 XSS Flaws and an 8.2 CI/CD Race Condition
GitLab's November 16 patch release fixes 37 CVEs, led by two CVSS 8.7 cross-site scripting flaws and a CVSS 8.2 CI/CD pipeline authorization race condition.
Overview
GitLab released versions 19.5.6, 19.4.8 and 19.3.9 of its Community Edition and Enterprise Edition on November 16, 2026, in a patch release the company says contains “important bug and security fixes” and that it “strongly recommend[s]” all self-managed installations apply immediately. The release notes list 37 distinct CVEs, four of them rated in the CVSS 7.0-8.9 high-severity band: two cross-site scripting (XSS) flaws scoring 8.7 each, an 8.2 authorization race condition in CI/CD pipeline jobs, and a 7.6 authorization flaw in workspaces. GitLab says GitLab.com, its hosted SaaS offering, is already running the patched version, and that GitLab Dedicated customers do not need to take action.
What We Know
- Two matching XSS flaws. CVE-2026-105739, affecting wiki pages, and CVE-2026-108153, affecting Error Tracking pages, each carry a CVSS 8.7 score with an identical vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N). GitLab’s advisory describes both the same way: an authenticated user could, “under certain conditions,” execute “arbitrary JavaScript in the browser of users viewing” the affected page, in each case “due to improper sanitization of user input.” The wiki flaw reaches back to version 17.2; the Error Tracking flaw reaches back to 16.1. NVD’s entry for CVE-2026-105739 carries the identical description, score and vector, independently confirming GitLab’s own listing.
- A race condition in CI/CD authorization. CVE-2026-18241, scored CVSS 8.2, is described by GitLab as allowing an authenticated user to “access protected CI/CD variables and resources due to a race condition in pipeline job authorization.” The affected version range goes back further than the other three high-severity flaws, to 9.3. NVD’s listing for the CVE matches GitLab’s description, score and vector string exactly.
- Workspace authorization exposing Kubernetes secrets. CVE-2026-97187, rated CVSS 7.6, could let an authenticated user “read Kubernetes Secrets from other namespaces in clusters connected through the GitLab agent for Kubernetes due to incorrect authorization in workspaces,” per GitLab’s advisory, affecting versions from 17.6 onward. NVD’s record again matches the description, score and vector.
- The remaining 33 CVEs. GitLab’s release notes rate the other 33 vulnerabilities Medium or Low; based on the scores published in the advisory, none reaches the 7.0 high-severity threshold. They span authorization and missing-authorization issues across CI/CD pipelines, package registries, and GitLab’s Duo Agent Platform features, plus a path-traversal flaw in GitLab Pages and an information-disclosure issue in GraphQL logging, per the advisory.
- Bug bounty credits. GitLab’s advisory credits researchers using the handles a0xnirudh (CVE-2026-105739), sunnybounty (CVE-2026-18241) and maxilagv (CVE-2026-97187) for reporting those three flaws through its HackerOne bug bounty program, per the advisory.
- No downtime expected. GitLab says the three patched versions “do not include any new migrations, and for multi-node deployments, should not require any downtime,” per the advisory.
What We Don’t Know
GitLab’s advisory does not specify what the “certain conditions” are for exploiting any of the four high-severity flaws, a standard qualifier GitLab attaches to each entry without further elaboration. The company’s policy, stated in the same release notes, is to make the full issue describing each vulnerability public on its issue tracker 90 days after the release that patched it, so additional technical detail on exploitation paths is not yet available. GitLab’s advisory does not state whether any of the 37 flaws have been exploited in the wild.
Context
This is the second time in five weeks that GitLab has shipped a patch release fixing dozens of CVEs at once: on October 12, 2026, the company patched CVE-2026-97229, a CVSS 10.0 code-execution flaw in its CI/CD regular expression compiler, as previously reported by The Machine Herald. GitLab’s own release notes describe its patch cadence as including both “scheduled releases,” issued “twice a month on the second and fourth Wednesdays,” and separate “ad-hoc critical patches for high-severity vulnerabilities,” per the advisory. None of the 37 CVEs in the November 16 release reaches the CVSS 9.0 threshold GitLab uses to classify a flaw as critical, based on the scores published in its own advisory.