Skip to main content
Mallory
← Back to News
internet-facing-service-vulnerabilitywidely-deployed-product-advisory

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 Fixes 37 Flaws, Including CI/CD Secret Exposure and Cross-Site Scripting

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.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

34 events · Nov 16, 2026 – Nov 17, 2026
  1. Nov 17, 202623h ago

    CVE record published for GitLab unassigned pipeline policy authorization bypass

    CVE-2026-85778 was published, detailing incorrect authorization that could allow an authenticated GitLab Enterprise Edition user to execute code in protected pipelines through a scheduled pipeline execution policy after it was unassigned. The medium-severity vulnerability (CVSS 6.2), reported by researcher tonydavis-sec, was fixed in versions 19.3.9, 19.4.8, and 19.5.6.

    CVE Record: CVE-2026-85778
  2. Nov 17, 202623h ago

    CVE record published for GitLab merge scheduling permission bypass

    CVE-2026-129321 was published, detailing insufficient permission enforcement that could allow authenticated GitLab CE/EE users with planner-role permissions to set future merge dates on their own merge requests, a capability requiring developer permissions or higher. The medium-severity vulnerability (CVSS 4.3), reported by researcher ser9q, was fixed in versions 19.3.9, 19.4.8, and 19.5.6.

    CVE Record: CVE-2026-129321
  3. Nov 17, 202623h ago

    CVE record published for GitLab Kubernetes proxy token-scope bypass

    CVE-2026-18491 was published, detailing missing granular scope enforcement that could allow authenticated GitLab CE/EE users with limited-scope personal access tokens to authorize Kubernetes API proxy access beyond their tokens' intended boundaries. The medium-severity vulnerability (CVSS 4.9), discovered internally by Alex Buijs, was fixed in versions 19.3.9, 19.4.8, and 19.5.6.

    CVE Record: CVE-2026-18491
  4. Nov 17, 202623h ago

    CVE record published for GitLab Confluence integration XSS

    CVE-2026-16609 was published, detailing improper input validation in GitLab CE/EE's Confluence integration that could allow an authenticated user with owner-role permissions to execute arbitrary JavaScript in another user's browser. The medium-severity vulnerability (CVSS 5.4), reported by researcher go7f0, was fixed in versions 19.3.9, 19.4.8, and 19.5.6.

    CVE Record: CVE-2026-16609
  5. Nov 17, 202623h ago

    CVE record published for GitLab group-import Owner membership bypass

    CVE-2026-129252 was published, detailing insufficient email verification during group-import member identity mapping that could grant authenticated users with unconfirmed email addresses Group Owner-level membership under certain conditions. The low-severity vulnerability (CVSS 3.7), reported by researcher iamgk808, was fixed in GitLab CE/EE versions 19.3.9, 19.4.8, and 19.5.6.

    CVE Record: CVE-2026-129252
  6. Nov 17, 202623h ago

    CVE record published for GitLab cross-namespace Kubernetes Secret exposure

    CVE-2026-97187 was published, detailing incorrect authorization in GitLab CE/EE workspaces that could allow authenticated users to read Kubernetes Secrets from other namespaces in connected clusters. The high-severity vulnerability (CVSS 7.6), reported by researcher maxilagv, was fixed in versions 19.3.9, 19.4.8, and 19.5.6.

    CVE Record: CVE-2026-97187
  7. Nov 17, 202623h ago

    CVE record published for GitLab Duo Workflow privilege escalation

    CVE-2026-128849 was published, detailing incorrect authorization that could allow authenticated GitLab Enterprise Edition users to start Duo Workflow sessions with privileges exceeding those declared by the foundational flow under certain client conditions. The medium-severity vulnerability (CVSS 4.3), discovered internally by Meir Benayoun, affected versions from 19.5 before 19.5.6 and was fixed in 19.5.6.

    CVE Record: CVE-2026-128849
  8. Nov 17, 202623h ago

    CVE record published for GitLab private-project package metadata exposure

    CVE-2026-16545 was published, detailing incorrect authorization checks that could allow unauthenticated GitLab CE/EE users to read private project metadata from packages published by other projects under certain conditions. The medium-severity vulnerability (CVSS 5.3) was fixed in versions 19.3.9, 19.4.8, and 19.5.6; GitLab credited researcher cl0ud_waldo with reporting it.

    CVE Record: CVE-2026-16545
  9. Nov 17, 202623h ago

    CVE record published for GitLab AI tool governance bypass

    CVE-2026-129253 was published, detailing improper binding of authorization tokens to workflow execution contexts that could allow authenticated GitLab Enterprise Edition users with developer permissions to bypass administrator-configured AI tool governance controls. The medium-severity vulnerability (CVSS 4.3), discovered internally by Rahul Barnwal, was fixed in versions 19.3.9, 19.4.8, and 19.5.6.

    CVE Record: CVE-2026-129253
  10. Nov 17, 202623h ago

    CVE record published for GitLab private-group iteration data exposure

    CVE-2026-104717 was published, detailing missing authorization checks that could allow authenticated GitLab Enterprise Edition users to view iteration details from private groups they cannot access. The medium-severity vulnerability (CVSS 4.3) was fixed in versions 19.3.9, 19.4.8, and 19.5.6; GitLab credited researcher theaikoisdead with reporting it.

    CVE Record: CVE-2026-104717
  11. Nov 17, 202623h ago

    CVE record published for GitLab Duo Agent Platform unredacted secret exposure

    CVE-2026-115736 was published, detailing improper authorization checks that could allow authenticated GitLab Enterprise Edition users to view unredacted secret values from secret detection findings they already can access through GitLab Duo Agent Platform. The medium-severity vulnerability (CVSS 4.3), discovered internally by RJ Coleman, was fixed in versions 19.3.9, 19.4.8, and 19.5.6.

    CVE Record: CVE-2026-115736
  12. Nov 17, 202623h ago

    CVE record published for GitLab Amazon Q administrator-lock bypass

    CVE-2026-115219 was published, detailing improper enforcement of instance-level settings that could allow a highly privileged authenticated user to enable Amazon Q automatic code reviews despite an administrator lock. The low-severity vulnerability (CVSS 3.8), discovered internally by Pratyaksh Golash, was fixed in GitLab Enterprise Edition versions 19.3.9, 19.4.8, and 19.5.6.

    CVE Record: CVE-2026-115219
  13. Nov 17, 202623h ago

    CVE record published for GitLab Duo Code Review consent-setting bypass

    CVE-2026-121948 was published, detailing incorrect authorization checks that could allow an authenticated user with high privileges to change a parent group's GitLab Duo Code Review consent setting under certain conditions. The low-severity vulnerability (CVSS 2.7), discovered internally by Tian Gao, was fixed in GitLab Enterprise Edition versions 19.3.9, 19.4.8, and 19.5.6.

    CVE Record: CVE-2026-121948
  14. Nov 17, 202623h ago

    CVE record published for GitLab agent server denial of service

    CVE-2026-115428 was published, detailing improper input validation that could let an authenticated user with a valid agent token trigger a NULL pointer dereference and denial of service in the GitLab agent server (KAS). The medium-severity vulnerability (CVSS 6.5), discovered internally by Clemens Beck, was fixed in GitLab CE/EE versions 19.3.9, 19.4.8, and 19.5.6.

    CVE Record: CVE-2026-115428
  15. Nov 17, 202623h ago

    CVE record published for GitLab Git LFS External Authorization bypass

    CVE-2026-110750 was published, detailing missing authorization checks that could allow authenticated GitLab CE/EE users to read Git LFS objects from projects restricted by External Authorization. The low-severity vulnerability (CVSS 2.2), reported by researcher 54v4n7, was fixed in versions 19.3.9, 19.4.8, and 19.5.6.

    CVE Record: CVE-2026-110750
  16. Nov 17, 202623h ago

    CVE record published for GitLab Pages cross-project artifact exposure

    CVE-2026-11768 was published, detailing improper file-path validation in GitLab CE/EE that could allow authenticated users to read other projects' private CI/CD job artifacts through GitLab Pages. The medium-severity vulnerability (CVSS 5.8), reported by researcher toofikz, was fixed in versions 19.3.9, 19.4.8, and 19.5.6.

    CVE Record: CVE-2026-11768
  17. Nov 17, 202623h ago

    CVE record published for GitLab private repository exposure through snippets

    CVE-2026-104934 was published, detailing missing authorization checks in GitLab CE/EE snippets that could expose private repository files under certain conditions. The medium-severity vulnerability (CVSS 4.3), reported by researcher dos4s, was fixed in versions 19.3.9, 19.4.8, and 19.5.6; the record inconsistently describes unauthenticated access while its CVSS vector requires low privileges.

    CVE Record: CVE-2026-104934
  18. Nov 17, 202623h ago

    CVE record published for GitLab CI/CD variable metadata exposure

    CVE-2026-101358 was published, detailing incorrect authorization in GitLab Enterprise Edition pipeline execution policies that could allow authenticated users to read CI/CD variable metadata from inaccessible projects. The low-severity vulnerability (CVSS 3.1) was fixed in versions 19.3.9, 19.4.8, and 19.5.6; GitLab credited researcher go7f0 with reporting it.

    CVE Record: CVE-2026-101358
  19. Nov 17, 202623h ago

    CVE record published for GitLab merge request diff manipulation

    CVE-2026-111747 was published, detailing improper file-name handling that could allow authenticated GitLab CE/EE users to hide changes from reviewers in merge request diffs under certain conditions. The low-severity vulnerability (CVSS 3.5) was fixed in versions 19.3.9, 19.4.8, and 19.5.6; GitLab credited researcher iamgk808 with reporting it.

    CVE Record: CVE-2026-111747
  20. Nov 17, 202623h ago

    CVE record published for GitLab repository import SSRF

    CVE-2026-126141 was published, detailing insufficient destination-address validation in GitLab CE/EE repository imports that could allow authenticated users to make requests to internal network services under certain conditions. The low-severity vulnerability (CVSS 3.5), discovered internally by Emma Park, was fixed in versions 19.3.9, 19.4.8, and 19.5.6.

    CVE Record: CVE-2026-126141
  21. Nov 17, 202623h ago

    CVE record published for GitLab GraphQL credential logging

    CVE-2026-110990 was published, detailing incomplete filtering that could cause sensitive credentials submitted in GitLab CE/EE GraphQL requests to be logged in plaintext. The low-severity vulnerability (CVSS 2.3) was fixed in versions 19.3.9, 19.4.8, and 19.5.6; GitLab credited researcher ericker with reporting it.

    CVE Record: CVE-2026-110990
  22. Nov 17, 202623h ago

    CVE record published for GitLab NuGet package metadata exposure

    CVE-2026-115218 was published, detailing missing authorization checks that could allow authenticated GitLab CE/EE users to read otherwise inaccessible NuGet package metadata under certain conditions. The medium-severity vulnerability (CVSS 4.3), discovered internally by Dzmitry (Dima) Meshcharakou, was fixed in versions 19.3.9, 19.4.8, and 19.5.6.

    CVE Record: CVE-2026-115218
  23. Nov 17, 202623h ago

    CVE record published for GitLab locked-discussion authorization bypass

    CVE-2026-102907 was published, detailing missing authorization checks that could allow authenticated GitLab CE/EE users to create issues with locked discussions without the required permissions. The medium-severity vulnerability (CVSS 4.3) was fixed in versions 19.3.9, 19.4.8, and 19.5.6; GitLab credited researcher r1skr1der with reporting it.

    CVE Record: CVE-2026-102907
  24. Nov 17, 202623h ago

    CVE record published for GitLab Duo usage analytics denial of service

    CVE-2026-125920 was published, detailing improper input validation that could allow authenticated GitLab Enterprise Edition users to cause a denial of service affecting Duo usage analytics under certain conditions. The medium-severity vulnerability (CVSS 4.3), discovered internally by Julie Huang, was fixed in versions 19.3.9, 19.4.8, and 19.5.6.

    CVE Record: CVE-2026-125920
  25. Nov 17, 202623h ago

    CVE record published for GitLab private CI/CD template exposure

    CVE-2026-108150 was published, detailing missing authorization checks that could allow authenticated GitLab CE/EE users to read private CI/CD template files from projects they cannot access. The medium-severity vulnerability (CVSS 4.3) was fixed in versions 19.3.9, 19.4.8, and 19.5.6; GitLab credited researcher js_noob with reporting it.

    CVE Record: CVE-2026-108150
  26. Nov 17, 202623h ago

    CVE record published for GitLab private-fork commit comment exposure

    CVE-2026-118961 was published, detailing missing authorization checks that could let unauthenticated users read private source-fork commit comments through a public project's merge request discussions under certain conditions. The medium-severity vulnerability (CVSS 5.3), discovered internally by Patrick Bajao, was fixed in GitLab CE/EE versions 19.3.9, 19.4.8, and 19.5.6.

    CVE Record: CVE-2026-118961
  27. Nov 17, 202623h ago

    CVE record published for GitLab Duo unlicensed-group settings bypass

    CVE-2026-122045 was published, detailing missing authorization checks that could allow authenticated GitLab Enterprise Edition users to configure GitLab Duo settings for groups without an eligible license under certain conditions. The medium-severity vulnerability (CVSS 4.3), discovered internally by Jessie Young, was fixed in versions 19.3.9, 19.4.8, and 19.5.6.

    CVE Record: CVE-2026-122045
  28. Nov 17, 202623h ago

    CVE record published for GitLab restricted job artifact data exposure

    CVE-2026-121533 was published, detailing missing authorization checks that could allow unauthenticated users to read restricted job artifact data in GitLab CE/EE under certain conditions. The medium-severity vulnerability (CVSS 5.3), discovered internally by Daniel Prause, was fixed in versions 19.3.9, 19.4.8, and 19.5.6.

    CVE Record: CVE-2026-121533
  29. Nov 17, 202623h ago

    CVE record published for GitLab Duo group access-rule bypass

    CVE-2026-122226 was published, detailing improper exception cleanup that could let authenticated GitLab Enterprise Edition users access restricted GitLab Duo features when group-based access-rule updates fail. The low-severity vulnerability (CVSS 2.2), discovered internally by Abhimanyu Singh, was fixed in versions 19.3.9, 19.4.8, and 19.5.6.

    CVE Record: CVE-2026-122226
  30. Nov 17, 202623h ago

    CVE record published for GitLab Duo cross-group data exposure

    CVE-2026-104902 was published, detailing improper authorization checks that could allow authenticated GitLab Enterprise Edition users to read other groups' GitLab Duo seat assignments and usage data. The medium-severity vulnerability (CVSS 4.3) was fixed in versions 19.3.9, 19.4.8, and 19.5.6; GitLab credited researcher 3nvz with reporting it.

    CVE Record: CVE-2026-104902
  31. Nov 17, 202623h ago

    CVE record published for GitLab restricted-project Git LFS data exposure

    CVE-2026-108155 was published, detailing incorrect authorization checks that could allow authenticated GitLab CE/EE users to read Git LFS objects from restricted projects under certain conditions. The medium-severity vulnerability (CVSS 4.3) was fixed in versions 19.3.9, 19.4.8, and 19.5.6; GitLab credited researcher 54v4n7 with reporting it.

    CVE Record: CVE-2026-108155
  32. Nov 17, 202623h ago

    CVE record published for GitLab repository import restriction bypass

    CVE-2026-108154 was published, detailing missing authorization checks that could let authenticated GitLab CE/EE users import repositories despite administrator restrictions on import sources. The medium-severity vulnerability (CVSS 4.3) was fixed in versions 19.3.9, 19.4.8, and 19.5.6; GitLab credited researcher 54v4n7 with reporting it.

    CVE Record: CVE-2026-108154
  33. Nov 17, 202623h ago

    CVE records added for three patched high-severity GitLab vulnerabilities

    Vulnerability histories recorded receipt from GitLab of CVE-2026-105739 and CVE-2026-108153, covering wiki and Error Tracking XSS, and CVE-2026-18241, covering a pipeline authorization race condition exposing protected CI/CD variables and resources. The records identify versions 19.3.9, 19.4.8, and 19.5.6 as containing fixes.

    CVE-2026-18241 - Incorrect Authorization in GitLab
  34. Nov 16, 20262d ago

    GitLab releases security patches fixing 37 vulnerabilities

    On November 16, GitLab released CE/EE versions 19.5.6, 19.4.8, and 19.3.9, fixing four high-, 24 medium-, and nine low-severity vulnerabilities, including wiki and Error Tracking XSS, protected CI/CD variable exposure, and cross-namespace Kubernetes Secret access. GitLab urged affected self-managed installations to upgrade immediately; GitLab.com was already patched, and Dedicated customers required no action.

    GitLab Patch Release: 19.5.6, 19.4.8, 19.3.9 | GitLab Docs
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.