GitLab Fixes 37 Flaws, Including CI/CD Secret Exposure and Cross-Site Scripting
Vulnerability Disclosure · 45 sources · Updated 3h ago · First seen Nov 17, 2026

GitLab released Community Edition and Enterprise Edition versions 19.5.6, 19.4.8, and 19.3.9, fixing 37 security vulnerabilities: four high, 24 medium, and nine low severity. The high-severity issues include a pipeline authorization race condition, CVE-2026-18241, that could let an authenticated user access protected CI/CD variables and resources under certain conditions, and a workspace vulnerability allowing cross-namespace access to Kubernetes Secrets. Two cross-site scripting flaws—CVE-2026-105739 in wiki pages and CVE-2026-108153 in Error Tracking—could allow authenticated attackers to execute arbitrary JavaScript in the browsers of users viewing affected pages. The pipeline race condition requires high attack complexity but no user interaction; the XSS flaws require a victim to view affected content.
Other fixes address authorization bypasses, private-data exposure, Maven package cache tampering, denial of service, server-side request forgery, and GitLab Duo privilege and governance weaknesses. Some affected functionality dates back to older GitLab releases, including version 9.3 for the pipeline race condition. Administrators of affected self-managed instances should upgrade immediately to a corrected release; Italy’s cybersecurity agency also urged prompt patching. GitLab.com is already patched, and GitLab Dedicated customers do not need to act. GitLab’s advisory does not report active exploitation.


