TL;DR
GitLab released versions 19.5.6, 19.4.8 and 19.3.9 on November 16, 2026, fixing 37 security vulnerabilities. This GitLab patch release covers both Community Edition (CE) and Enterprise Edition (EE). The two most severe flaws are cross-site scripting bugs rated CVSS 8.7.
GitLab fixed 2 high-severity cross-site scripting (XSS) bugs, a CI/CD race condition rated 8.2, and 34 medium and low issues. GitLab.com already runs the fix, and GitLab Dedicated customers need no action. GitLab reports no exploitation, and no public proof-of-concept has been confirmed.
- Total: 37 CVEs
- Severity: 4 High · 24 Medium · 9 Low
- Actively exploited: None confirmed
- Highest severity: 8.7 (High · CVSSv3) — CVE-2026-105739
- Action: Apply the latest security updates now
Notable CVEs
| CVE | CVSS (CVSSv3) | Type | Status |
|---|---|---|---|
| CVE-2026-105739 | 8.7 | CWE-79 | Not exploited |
| CVE-2026-108153 | 8.7 | CWE-79 | Not exploited |
| CVE-2026-18241 | 8.2 | CWE-863 | Not exploited |
| CVE-2026-97187 | 7.6 | CWE-863 | Not exploited |
| CVE-2026-115428 | 6.5 | CWE-476 | Not exploited |
| CVE-2026-85778 | 6.2 | CWE-863 | Not exploited |
| CVE-2026-112203 | 5.9 | CWE-349 | Not exploited |
| CVE-2026-11768 | 5.8 | CWE-22 | Not exploited |
Why It Matters
GitLab hosts source code, CI/CD pipelines and secrets for many development teams. As a result, even small authorization gaps can expose private code or credentials. GitLab itself urges action. According to the GitLab patch release notes, “we strongly recommend that all self-managed GitLab installations be upgraded to one of these versions immediately.”
This GitLab patch release also follows a busy few weeks. GitLab shipped critical patch releases in October and early November, including 19.5.1 and 19.5.4.
How the Attack Works
Cross-Site Scripting in Wiki and Error Tracking
CVE-2026-105739 sits in wiki pages. GitLab says it “could have allowed an authenticated user to execute arbitrary JavaScript in the browser of users viewing a wiki page.” CVE-2026-108153 works the same way in Error Tracking pages. In both cases, the attacker needs an account, and the victim must view the page.
Race Condition in CI/CD Jobs
CVE-2026-18241 (CVSS 8.2) involves a race condition in pipeline job authorization. An authenticated user could reach “protected CI/CD variables and resources.” Protected variables often hold deployment keys and tokens, so this flaw deserves attention.
Kubernetes Secrets Exposure
CVE-2026-97187 (CVSS 7.6) affects workspaces. An authenticated user could read Kubernetes Secrets from other namespaces in clusters linked through the GitLab agent. However, this flaw requires high privileges.
Flaws Without Login
Several medium-severity bugs need no login. CVE-2026-118961 exposes commit comments from a private fork through a public merge request. Similarly, CVE-2026-121533 leaks restricted job artifact data, and CVE-2026-16545 leaks private package metadata. Each scores 5.3.
Other Notable Fixes
CVE-2026-11768 lets a user read other projects’ private job artifacts through a path traversal in GitLab Pages. Meanwhile, CVE-2026-112203 lets an upstream repository owner alter cached Maven packages in a shared virtual registry. Many smaller fixes target GitLab Duo AI features, the MCP server and Git LFS.
Who Found the Flaws
Outside researchers reported 21 of the 37 flaws through GitLab’s HackerOne bug bounty program. For example, researcher a0xnirudh found both high-severity XSS bugs. GitLab’s own team found the other 16 internally.
The split shows how much of GitLab’s attack surface now sits in newer features. Notably, nine fixes touch GitLab Duo, including the Duo Agent Platform, Code Review and Amazon Q integration. In addition, one fix covers the GitLab MCP server, which connects AI agents to GitLab data.
Exploitation Status
GitLab does not report any attacks using these flaws. None appear in CISA’s Known Exploited Vulnerabilities catalog. Even so, admins should not wait for proof of attacks before they patch.
Affected Versions
Each flaw has its own starting version, some reaching back to GitLab 8.0. All affected branches share the same fixed releases:
- GitLab CE/EE 19.5 before 19.5.6
- GitLab CE/EE 19.4 before 19.4.8
- GitLab CE/EE 19.3 before 19.3.9, plus earlier releases back to each flaw’s starting version
Thirteen of the fixes affect only GitLab EE, mostly in GitLab Duo and pipeline execution policies. The other 24 affect both CE and EE.
Patch and Mitigation
Upgrade Self-Managed Instances
Upgrade self-managed GitLab to 19.5.6, 19.4.8 or 19.3.9. GitLab notes that when no deployment type is named, “it means all types are affected.” That includes Omnibus, source and Helm chart installs.
Reduce Exposure Until You Patch
- Review who can edit wikis and Error Tracking settings.
- Rotate protected CI/CD variables if you suspect misuse.
- Check Kubernetes agent permissions for workspaces.
- Limit public projects that fork private code.
GitLab will publish the issue details 90 days after release. Therefore, apply this GitLab patch release before those details become public.
Support Our Threat Intelligence
Find our vulnerability reports and weekly recaps helpful? Support our work today and unlock a 100% ad-free reading experience!