GitLab released versions 19.5.6, 19.4.8, and 19.3.9 on November 16, 2026. These updates address 37 security vulnerabilities across both the Community Edition and the Enterprise Edition.
The fixes include four high-severity issues, 24 medium-severity issues, and nine low-severity issues that affect development infrastructure, integrations, and AI features. Self-managed administrators should upgrade immediately. GitLab.com has patched the platform, and dedicated customers do not need to take any action.
The release continues a series of fixes targeting CI/CD authorization and data exposure. Among the latest vulnerabilities, CVE-2026-18241 exposes protected pipeline variables and resources through a race condition in job authorization. Rated 8.2, it requires authentication but no user interaction, and its high attack complexity distinguishes it from the release’s browser-based flaws.
High-Severity Vulnerabilities
The four high-severity vulnerabilities affect both editions. Their affected-version starting points differ, but each is remediated in the three newly released versions.
| CVE | CVSS | Component | Technical impact | Affected starting version |
|---|---|---|---|---|
| CVE-2026-105739 | 8.7 High | Wiki pages | JavaScript execution through unsanitized input | 17.2 |
| CVE-2026-108153 | 8.7 High | Error Tracking | JavaScript execution through unsanitized input | 16.1 |
| CVE-2026-18241 | 8.2 High | CI/CD jobs | Protected variable and resource access through authorization race | 9.3 |
| CVE-2026-97187 | 7.6 High | Workspaces | Reading Kubernetes Secrets across namespaces | 17.6 |
All rows cover affected releases before 19.3.9, 19.4.8, or 19.5.6 within their respective branches.
The two 8.7-rated cross-site scripting vulnerabilities allow authenticated attackers to execute arbitrary JavaScript when victims view affected pages. Both require user interaction and stem from improper input sanitization. Earlier GitLab stored XSS vulnerabilities similarly demonstrated how browser-facing development features can become attack surfaces.
CVE-2026-97187 concerns workspace authorization rather than browser execution. Under specific conditions, an authenticated user with high privileges could read Kubernetes Secrets from other namespaces in clusters connected through the GitLab agent. GitLab credits researcher maxilagv with reporting the issue through its HackerOne program.
Beyond the high-severity issues, GitLab’s official security advisory details CVE-2026-11768, a medium-severity path traversal vulnerability in GitLab Pages. Improper file-path validation could let authenticated users read private CI/CD artifacts belonging to other projects. The flaw carries a 5.8 score and affects releases dating to version 12.4.
The MCP server fix addresses CVE-2026-123142, rated 4.3. An authenticated user holding an MCP-scoped OAuth token could perform unauthorized issue and merge-request state changes, including approvals and merges. Unlike separately reported MCP server vulnerabilities, this issue specifically involves GitLab’s authorization checks, not a disclosed command-execution primitive.
Additional fixes cover package registries, Kubernetes proxy access, Duo governance, repository imports, and plaintext credential logging. These expand the update’s scope beyond pipelines, echoing earlier GitLab integration security issues.
GitLab says the releases introduce no new migrations, although default Omnibus upgrade behavior still stops and restarts services. Detailed vulnerability issues become public 90 days after patching.
All cve table data
| CVE ID | Severity | CVSS | Affected component | Vulnerability / Security impact |
|---|---|---|---|---|
| CVE-2026-105739 | High | 8.7 | Wiki pages | Improper input sanitization allows authenticated users to execute arbitrary JavaScript in visitors’ browsers. |
| CVE-2026-108153 | High | 8.7 | Error Tracking | Improper input sanitization allows authenticated users to execute arbitrary JavaScript in browsers viewing Error Tracking pages. |
| CVE-2026-18241 | High | 8.2 | CI/CD pipeline jobs | A race condition in job authorization allows authenticated users to access protected CI/CD variables and resources. |
| CVE-2026-97187 | High | 7.6 | Workspaces | Incorrect authorization allows authenticated users to read Kubernetes Secrets from other namespaces in connected clusters. |
| CVE-2026-115428 | Medium | 6.5 | GitLab agent server (KAS) | A NULL pointer dereference allows authenticated users with valid agent tokens to cause denial of service. |
| CVE-2026-85778 | Medium | 6.2 | Scheduled pipeline execution policies | Incorrect authorization allows authenticated users to run code in protected pipelines after the associated policy has been unassigned. |
| CVE-2026-112203 | Medium | 5.9 | Maven virtual registry | Improper response validation allows an attacker controlling an upstream repository to alter cached packages from other repositories in the same virtual registry. |
| CVE-2026-11768 | Medium | 5.8 | GitLab Pages | Path traversal allows authenticated users to read private CI/CD job artifacts belonging to other projects. |
| CVE-2026-16609 | Medium | 5.4 | Confluence integration | Improper input validation allows authenticated users with owner-role permissions to execute JavaScript in another user’s browser. |
| CVE-2026-118961 | Medium | 5.3 | Merge request discussions | Missing authorization allows unauthenticated users to read private source-fork commit comments through public-project merge request discussions. |
| CVE-2026-121533 | Medium | 5.3 | Job artifacts | Missing authorization allows unauthenticated users to read restricted job artifact data. |
| CVE-2026-16545 | Medium | 5.3 | Package Registry | Incorrect authorization allows unauthenticated users to read private-project metadata through packages published by other projects. |
| CVE-2026-18491 | Medium | 4.9 | GitLab agent for Kubernetes | Missing granular scope enforcement allows limited-scope personal access tokens to authorize Kubernetes API proxy access beyond their intended boundaries. |
| CVE-2026-115736 | Medium | 4.3 | GitLab Duo Agent Platform | Improper authorization exposes unredacted secret values from secret detection findings accessible to the authenticated user. |
| CVE-2026-115218 | Medium | 4.3 | NuGet package registry | Missing authorization allows authenticated users to read otherwise inaccessible NuGet package metadata. |
| CVE-2026-104902 | Medium | 4.3 | GitLab Duo seat management | Improper authorization allows authenticated users to read other groups’ Duo seat assignments and usage data. |
| CVE-2026-104934 | Medium | 4.3 | Snippets | Missing authorization can expose files from a project’s private repository. GitLab’s description identifies unauthenticated access, although its CVSS vector specifies low privileges. |
| CVE-2026-108150 | Medium | 4.3 | CI/CD templates | Missing authorization allows authenticated users to read private CI/CD template files from inaccessible projects. |
| CVE-2026-108155 | Medium | 4.3 | Git LFS | Incorrect authorization allows authenticated users to read Git LFS objects from restricted projects. |
| CVE-2026-104717 | Medium | 4.3 | Iterations | Missing authorization allows authenticated users to view iteration details from inaccessible private groups. |
| CVE-2026-102907 | Medium | 4.3 | Issues | Improper authorization allows authenticated users to create issues with locked discussions without the required permissions. |
| CVE-2026-125920 | Medium | 4.3 | GitLab Duo usage analytics | Improper input quantity validation allows authenticated users to cause denial of service affecting Duo usage analytics. |
| CVE-2026-108154 | Medium | 4.3 | Project import | Missing authorization allows authenticated users to import Git repositories despite administrator restrictions on import sources. |
| CVE-2026-129253 | Medium | 4.3 | GitLab Duo Agent Platform | Improper token-to-workflow binding allows developer-role users to bypass administrator-configured AI tool governance controls. |
| CVE-2026-129321 | Medium | 4.3 | Merge request scheduling | Insufficient permission enforcement allows planner-role users to schedule future merges for their own merge requests. |
| CVE-2026-123142 | Medium | 4.3 | GitLab MCP server | Incorrect authorization allows MCP-scoped OAuth tokens to perform unauthorized issue and merge-request state changes, including approvals and merges. |
| CVE-2026-122045 | Medium | 4.3 | GitLab Duo group settings | Missing authorization allows authenticated users to configure Duo settings for groups without eligible licenses. |
| CVE-2026-128849 | Medium | 4.3 | GitLab Duo Agent Platform flows | Improper privilege-boundary enforcement allows authenticated users to start Duo Workflow sessions with privileges exceeding those declared by the foundational flow. |
| CVE-2026-115219 | Low | 3.8 | GitLab Duo with Amazon Q | Improper enforcement of instance settings allows authenticated users to enable automatic code reviews despite an administrator lock. |
| CVE-2026-129252 | Low | 3.7 | Group import member email mapping | Insufficient email verification can grant authenticated users with unconfirmed email addresses Group Owner membership during imports. |
| CVE-2026-111747 | Low | 3.5 | Merge request diffs | Improper filename handling allows authenticated users to hide changes from reviewers. |
| CVE-2026-126141 | Low | 3.5 | Repository import | Insufficient destination-address validation allows authenticated users to make server-side requests to internal network services. |
| CVE-2026-101358 | Low | 3.1 | Pipeline execution policies | Improper authorization allows authenticated users to read CI/CD variable metadata from inaccessible projects. |
| CVE-2026-121948 | Low | 2.7 | GitLab Duo Code Review | Incorrect authorization allows authenticated users to change a parent group’s Duo Code Review consent setting. |
| CVE-2026-110990 | Low | 2.3 | GraphQL logging | Incomplete filtering allows sensitive credentials submitted in GraphQL requests to be logged in plaintext. |
| CVE-2026-122226 | Low | 2.2 | GitLab Duo access rules | Improper handling of failed access-rule updates allows authenticated users to access Duo features restricted by group-based rules. |
| CVE-2026-110750 | Low | 2.2 | Git LFS | Missing authorization allows authenticated users to read Git LFS objects from projects restricted by External Authorization. |
Give your SOC the alert context on the latest threats to stop incidents quickly -> Integrate Threat Intel from 16K SOCs:

