On this page · 10 sections
- Wiki pages and Error Tracking: XSS in viewers' browsers
- CI/CD pipeline jobs and workspaces: High-severity authorization flaws
- GitLab agent, pipeline policies and CI/CD templates: Medium-severity fixes
- Pages, job artifacts, Git LFS, snippets and package registries: read access to private data
- GitLab Duo and Amazon Q: AI feature access controls
- Issues, merge requests and imports: authorization and validation fixes
- Checking Self-Managed GitLab Installs Against the Affected Ranges
- Upgrading GitLab to 19.5.6, 19.4.8 or 19.3.9
- Also in this release
- Sources
Security release
Status as of 2026-11-17
37 CVEs
GitLab
- First fixed in
- 19.3.9, 19.4.8, 19.5.6The earliest release on each line that fixes these CVEs. The release to install is in the article's upgrade steps.
- Published
- 2026-11-17
Most severe first
- CVE-2026-105739High8.7Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in GitLab
- CVE-2026-108153High8.7Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in GitLab
- CVE-2026-18241High8.2Incorrect Authorization in GitLab
- CVE-2026-97187High7.6Incorrect Authorization in GitLab
- CVE-2026-115428Medium6.5NULL Pointer Dereference in GitLab
Show all 37
- CVE-2026-85778Medium6.2Incorrect Authorization in GitLab
- CVE-2026-112203Medium5.9Acceptance of Extraneous Untrusted Data With Trusted Data in GitLab
- CVE-2026-11768Medium5.8Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLab
- CVE-2026-16609Medium5.4Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in GitLab
- CVE-2026-118961Medium5.3Missing Authorization in GitLab
- CVE-2026-121533Medium5.3Missing Authorization in GitLab
- CVE-2026-16545Medium5.3Incorrect Authorization in GitLab
- CVE-2026-18491Medium4.9Incorrect Authorization in GitLab
- CVE-2026-102907Medium4.3Missing Authorization in GitLab
- CVE-2026-104717Medium4.3Missing Authorization in GitLab
- CVE-2026-104902Medium4.3Authorization Bypass Through User-Controlled Key in GitLab
- CVE-2026-104934Medium4.3Missing Authorization in GitLab
- CVE-2026-108150Medium4.3Missing Authorization in GitLab
- CVE-2026-108154Medium4.3Missing Authorization in GitLab
- CVE-2026-108155Medium4.3Incorrect Authorization in GitLab
- CVE-2026-115218Medium4.3Missing Authorization in GitLab
- CVE-2026-115736Medium4.3Authorization Bypass Through User-Controlled Key in GitLab
- CVE-2026-122045Medium4.3Missing Authorization in GitLab
- CVE-2026-123142Medium4.3Incorrect Authorization in GitLab
- CVE-2026-125920Medium4.3Improper Validation of Specified Quantity in Input in GitLab
- CVE-2026-128849Medium4.3Incorrect Authorization in GitLab
- CVE-2026-129253Medium4.3Incorrect Authorization in GitLab
- CVE-2026-129321Medium4.3Insufficient Granularity of Access Control in GitLab
- CVE-2026-115219Low3.8Reliance on Untrusted Inputs in a Security Decision in GitLab
- CVE-2026-129252Low3.7Authentication Bypass by Spoofing in GitLab
- CVE-2026-111747Low3.5Use of Incorrectly-Resolved Name or Reference in GitLab
- CVE-2026-126141Low3.5Server-Side Request Forgery (SSRF) in GitLab
- CVE-2026-101358Low3.1Incorrect Authorization in GitLab
- CVE-2026-121948Low2.7Incorrect Authorization in GitLab
- CVE-2026-110990Low2.3Insertion of Sensitive Information into Log File in GitLab
- CVE-2026-110750Low2.2Missing Authorization in GitLab
- CVE-2026-122226Low2.2Improper Cleanup on Thrown Exception in GitLab
Data: CVE records on cve.org
Warning
Self-managed GitLab CE and EE installations running an affected version are exposed. The GitLab patch release notes rate four issues as High: cross-site scripting in wiki pages and in Error Tracking, and incorrect authorization in CI/CD pipeline jobs and workspaces. GitLab recommends upgrading to 19.5.6, 19.4.8 or 19.3.9 as soon as possible.
Wiki pages and Error Tracking: XSS in viewers' browsers #
The two High-severity cross-site scripting issues let an authenticated user run JavaScript in the browser of other users. The first affects wiki pages. The CVE-2026-105739 record, published 2026-11-17 by GitLab, gives a CVSS 3.1 base score of 8.7 (HIGH), assigned by GitLab, and describes the flaw as a case where the user could
execute arbitrary JavaScript in the browser of users viewing a wiki page
The affected range is all versions from 17.2 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6. The patch notes give the same range and the CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N.
The Error Tracking issue, CVE-2026-108153, has the same CVSS 3.1 base score of 8.7 (HIGH), assigned by GitLab, in its record. It applies to users viewing Error Tracking pages, with an affected range of all versions from 16.1 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6. Because the range starts at 16.1, installations on older lines are covered as well. The patch notes credit a0xnirudh with reporting both XSS issues through GitLab's HackerOne bug bounty program.
CI/CD pipeline jobs and workspaces: High-severity authorization flaws #
Two High-severity incorrect authorization issues expose secrets and protected resources. The CVE-2026-18241 record gives a CVSS 3.1 base score of 8.2 (HIGH), assigned by GitLab, and states that an authenticated user could access protected CI/CD variables and resources. The affected range is all versions from 9.3 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6, so a pipeline setup that relies on protected variables is in scope on every listed line.
Note
Background: The CVE-2026-18241 record ties the access to a race condition in pipeline job authorization. The patch notes list this issue's affected range as all versions from 9.3 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6.
The workspaces issue, CVE-2026-97187, has a CVSS 3.1 base score of 7.6 (HIGH), assigned by GitLab, in its record. An authenticated user could read Kubernetes Secrets from other namespaces in clusters connected through the GitLab agent for Kubernetes. The affected range is all versions from 17.6 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6. Teams that connect clusters through the agent should treat this as a cross-namespace secret exposure. The patch notes credit sunnybounty with the CI/CD pipeline jobs report and maxilagv with the workspaces report, both made through GitLab's HackerOne bug bounty program.
GitLab agent, pipeline policies and CI/CD templates: Medium-severity fixes #
The CVE-2026-115428 record covers a denial of service in the GitLab agent server (KAS). It gives a CVSS 3.1 base score of 6.5 (MEDIUM), assigned by GitLab, and says an authenticated user with a valid agent token could cause it through improper input validation, in all versions from 17.2 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6.
The Kubernetes agent proxy-user flow has its own fix in CVE-2026-18491, a record with a CVSS 3.1 base score of 4.9 (MEDIUM), assigned by GitLab. It lets a granular personal access token with limited scope authorize Kubernetes API proxy access beyond its boundaries, for versions from 19.2 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6.
The scheduled pipeline execution policy fix, CVE-2026-85778, is EE only. Its record gives a CVSS 3.1 base score of 6.2 (MEDIUM), assigned by GitLab, and describes an authenticated user running code in protected pipelines after the policy had been unassigned. The affected range is all versions from 19.1 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6.
The CVE-2026-108150 record covers CI/CD template files: an authenticated user could read private templates from projects they could not access, with a CVSS 3.1 base score of 4.3 (MEDIUM), assigned by GitLab, for versions from 13.12 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6. The patch notes also list CVE-2026-101358, a Low EE issue in pipeline execution policies that exposed CI/CD variable metadata, for versions from 17.10 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6.
Pages, job artifacts, Git LFS, snippets and package registries: read access to private data #
Several Medium fixes stop users from reading content they should not reach. The CVE-2026-11768 record (CVSS 3.1 base score 5.8, MEDIUM, assigned by GitLab) covers GitLab Pages: an authenticated user could read private CI/CD job artifacts belonging to other projects, for versions from 12.4 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6. The CVE-2026-121533 record (CVSS 3.1 base score 5.3, MEDIUM, assigned by GitLab) covers job artifacts, where an unauthenticated user could read restricted artifact data, for versions from 13.8 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6.
Package and repository data follow the same pattern. The CVE-2026-16545 record (CVSS 3.1 base score 5.3, MEDIUM) says an unauthenticated user could read private project metadata from packages published by other projects, for versions from 12.10 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6. The CVE-2026-115218 record (CVSS 3.1 base score 4.3, MEDIUM) covers NuGet package metadata for versions from 13.8 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6.
The CVE-2026-108155 record (CVSS 3.1 base score 4.3, MEDIUM) covers Git LFS objects from restricted projects, for versions from 8.12 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6. The CVE-2026-104934 record (CVSS 3.1 base score 4.3, MEDIUM) covers files from a project's private repository, reachable without authentication through snippets, for versions from 19.0 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6.
The Maven virtual registry issue is EE only. The CVE-2026-112203 record gives a CVSS 3.1 base score of 5.9 (MEDIUM), assigned by GitLab, and says that an individual controlling an upstream repository could alter cached Maven packages from other repositories in the same virtual registry, for versions from 18.2 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6.
Note
Background: The CVE-2026-112203 record attributes the Maven issue to improper response validation. The record describes the actor as an individual controlling an upstream repository, and the effect as altering cached Maven packages from other repositories in the same virtual registry.
GitLab Duo and Amazon Q: AI feature access controls #
The two Duo records here, CVE-2026-115736 and CVE-2026-104902, both apply to GitLab EE only. The CVE-2026-115736 record (CVSS 3.1 base score 4.3, MEDIUM, assigned by GitLab) says an authenticated user could view unredacted secret values from secret detection findings through GitLab Duo Agent Platform, for versions from 19.1 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6. The CVE-2026-104902 record (CVSS 3.1 base score 4.3, MEDIUM, assigned by GitLab) covers Duo seat assignments and usage data of other groups, for versions from 17.7 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6.
The patch notes list further Duo fixes that have no record among the sources. CVE-2026-128849 is a Medium issue that affects only the 19.5 line, all versions from 19.5 before 19.5.6, and lets an authenticated user start a Duo Workflow session with privileges beyond those the foundational flow declares, in certain client environments. CVE-2026-129253 (Medium) lets a developer-role user bypass admin-configured AI tool governance controls in a governed namespace, from 19.1 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6. CVE-2026-115219 (Low) lets an authenticated user enable Amazon Q automatic code reviews despite an administrator lock, from 19.2 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6.
CVE-2026-122045 (Medium) allows group Duo settings without an eligible license, from 16.10 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6. CVE-2026-125920 (Medium) lets an authenticated user cause a denial of service affecting Duo usage analytics, from 17.4 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6. CVE-2026-121948 (Low) lets an authenticated user change the GitLab Duo Code Review consent setting of a parent group, from 19.2 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6. CVE-2026-122226 (Low) lets an authenticated user access GitLab Duo features restricted by group-based access rules, from 18.8 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6.
Issues, merge requests and imports: authorization and validation fixes #
The CVE-2026-118961 record (CVSS 3.1 base score 5.3, MEDIUM, assigned by GitLab) covers an unauthenticated user reading commit comments from a private source fork through a public project's merge request discussions, for versions from 17.11 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6. The CVE-2026-16609 record (CVSS 3.1 base score 5.4, MEDIUM) covers the Confluence integration, where an authenticated user with owner-role permissions could run JavaScript in another user's browser, for versions from 13.2 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6.
The remaining items come from the patch notes only. A Medium MCP server issue (CVE-2026-123142) lets a user with an MCP-scoped OAuth token change issuable states, including approving and merging. Medium issues cover issues with locked discussions (CVE-2026-102907), iterations in private groups (CVE-2026-104717, EE), project import despite administrator import-source restrictions (CVE-2026-108154), and merge request scheduling by planner-role users (CVE-2026-129321).
Low issues cover group import member mapping, which could grant Group Owner membership to a user with an unconfirmed email (CVE-2026-129252; all versions before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6), merge request diffs that could hide changes (CVE-2026-111747), and SSRF through repository import (CVE-2026-126141). GraphQL logging (CVE-2026-110990, Low, from 17.1.7 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6) let credential values reach logs in plaintext. CVE-2026-110750 (Low) lets an authenticated user read Git LFS objects from projects restricted by External Authorization, from 11.2 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6.
Checking Self-Managed GitLab Installs Against the Affected Ranges #
The table that follows is a partial summary of four High issues and one Medium issue. Compare the installed version with the affected range of each issue in the sections above and in the patch notes. An installation is in scope when its version falls inside a range for a flaw, for example a 19.5 install below 19.5.6 is in the 19.5 range of every High issue. The patch notes say that when no deployment type is named, all types are affected, so Omnibus, source, and Helm chart installations are all in scope. GitLab.com already runs the patched version, and GitLab Dedicated customers need no action.
| Issue (CVE) | Severity | Affected versions, as stated | Fixed in |
|---|---|---|---|
| Wiki pages XSS (CVE-2026-105739) | High | From 17.2 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 | 19.3.9, 19.4.8 and 19.5.6 on their lines |
| Error Tracking XSS (CVE-2026-108153) | High | From 16.1 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 | 19.3.9, 19.4.8 and 19.5.6 on their lines |
| CI/CD pipeline jobs (CVE-2026-18241) | High | From 9.3 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 | 19.3.9, 19.4.8 and 19.5.6 on their lines |
| Workspaces (CVE-2026-97187) | High | From 17.6 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 | 19.3.9, 19.4.8 and 19.5.6 on their lines |
| Agent server denial of service (CVE-2026-115428) | Medium | From 17.2 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 | 19.3.9, 19.4.8 and 19.5.6 on their lines |
The CVE records linked above are 19 of the 37 CVEs named in the patch notes, all published 2026-11-17 by GitLab. Their CVSS 3.1 scores are those GitLab assigned. The records for the other 18 CVEs are not among the sources, so this article gives no scores for them.
Upgrading GitLab to 19.5.6, 19.4.8 or 19.3.9 #
- Move each installation to the patch release of its own line: 19.3.x to 19.3.9, 19.4.x to 19.4.8, or 19.5.x to 19.5.6.
- Installations on a line older than 19.3 get no patch release of their own here, although most affected ranges reach back well before 19.3. The patch notes say GitLab strongly recommends that all self-managed GitLab installations be upgraded to one of these versions immediately.
- Before the update, check whether Omnibus should run its automatic reconfigure. By default, Omnibus packages stop, run migrations, and start again. To change this, add the file
/etc/gitlab/skip-auto-reconfigure; the notes say it is only used for updates. - Expect no new migrations. For multi-node deployments, the notes say the update should not require any downtime.
- Update GitLab Runner separately, following the Updating the Runner page named in the patch notes.
Also in this release #
- 19.5.6: exiftool 13.59; NGINX 1.31.4 to 1.31.7; curl 8.23.0; libxslt 1.1.43 to 1.1.45; libtiff 4.7.1 to 4.7.2; GnuPG 2.5.24 and related libraries.
- 19.5.6: webauthn gem 3.4.4; rack limiter logs client address, path and method; code-owner gate skips can_push_to_branch? on large pushes; commit page pipelines badge capped at 1,000+; protected branch push check skips per-ref Redis cache; SAML admin groups re-evaluated on Admin Mode re-entry; Orbit docs links; Docker images with Docker media types for Podman.
- 19.4.8: exiftool 13.59; NGINX 1.31.7; curl 8.23.0; libxslt 1.1.45; libtiff 4.7.2; GnuPG 2.5.24 and related libraries; SELinux module policy format pinned to 19.
- 19.4.8: webauthn gem 3.4.4; rack middleware logs blocked requests; code-owner gate reorder; commit page badge cap; Orbit docs links; Docker media types for Podman.
- 19.3.9: exiftool 13.59; NGINX 1.31.7; curl 8.23.0; libtiff 4.7.2; libxslt 1.1.45; GnuPG 2.5.24 and related libraries; SELinux module policy format pinned to 19.
- 19.3.9: oj 3.17.8 for native memory-safety bugs; sast_iac mapped to sast in approval policy rules; webauthn gem 3.4.4; Docker media types for Podman.
The complete list is in the GitLab patch release notes.
The Sentinel’s Call
Self-managed installations on 19.3, 19.4 or 19.5 should move to the patch release of their line now, and older installations to one of the three patched versions. Start with the four High issues, whose CVE records give CVSS 3.1 scores of 8.7 for wiki pages, 8.7 for Error Tracking, 8.2 for CI/CD pipeline jobs and 7.6 for workspaces, all assigned by GitLab. The Medium and Low items ship in the same patch releases, so they need no separate step.
Our judgement, drawn only from the facts and sources above.
Sources
- GitLab Patch Release: 19.5.6, 19.4.8, 19.3.9 | GitLab Docs docs.gitlab.com · Nov 16, 2026
- CVE-2026-105739: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in GitLab cve.org · Nov 17, 2026
- CVE-2026-108153: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in GitLab cve.org · Nov 17, 2026
- CVE-2026-18241: Incorrect Authorization in GitLab cve.org · Nov 17, 2026
- CVE-2026-97187: Incorrect Authorization in GitLab cve.org · Nov 17, 2026
- CVE-2026-115428: NULL Pointer Dereference in GitLab cve.org · Nov 17, 2026
- CVE-2026-85778: Incorrect Authorization in GitLab cve.org · Nov 17, 2026
- CVE-2026-112203: Acceptance of Extraneous Untrusted Data With Trusted Data in GitLab cve.org · Nov 17, 2026
- CVE-2026-11768: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLab cve.org · Nov 17, 2026
- CVE-2026-16609: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in GitLab cve.org · Nov 17, 2026
- CVE-2026-118961: Missing Authorization in GitLab cve.org · Nov 17, 2026
- CVE-2026-121533: Missing Authorization in GitLab cve.org · Nov 17, 2026
- CVE-2026-16545: Incorrect Authorization in GitLab cve.org · Nov 17, 2026
- CVE-2026-18491: Incorrect Authorization in GitLab cve.org · Nov 17, 2026
- CVE-2026-115736: Authorization Bypass Through User-Controlled Key in GitLab cve.org · Nov 17, 2026
- CVE-2026-115218: Missing Authorization in GitLab cve.org · Nov 17, 2026
- CVE-2026-104902: Authorization Bypass Through User-Controlled Key in GitLab cve.org · Nov 17, 2026
- CVE-2026-104934: Missing Authorization in GitLab cve.org · Nov 17, 2026
- CVE-2026-108150: Missing Authorization in GitLab cve.org · Nov 17, 2026
- CVE-2026-108155: Incorrect Authorization in GitLab cve.org · Nov 17, 2026
Also consulted
- CVE-2026-104717: Missing Authorization in GitLab cve.org · Nov 17, 2026
- CVE-2026-102907: Missing Authorization in GitLab cve.org · Nov 17, 2026
- CVE-2026-125920: Improper Validation of Specified Quantity in Input in GitLab cve.org · Nov 17, 2026
- CVE-2026-108154: Missing Authorization in GitLab cve.org · Nov 17, 2026
- CVE-2026-129253: Incorrect Authorization in GitLab cve.org · Nov 17, 2026
- CVE-2026-129321: Insufficient Granularity of Access Control in GitLab cve.org · Nov 17, 2026
- CVE-2026-123142: Incorrect Authorization in GitLab cve.org · Nov 17, 2026
- CVE-2026-122045: Missing Authorization in GitLab cve.org · Nov 17, 2026
- CVE-2026-128849: Incorrect Authorization in GitLab cve.org · Nov 17, 2026
- CVE-2026-115219: Reliance on Untrusted Inputs in a Security Decision in GitLab cve.org · Nov 17, 2026
- CVE-2026-129252: Authentication Bypass by Spoofing in GitLab cve.org · Nov 17, 2026
- CVE-2026-111747: Use of Incorrectly-Resolved Name or Reference in GitLab cve.org · Nov 17, 2026
- CVE-2026-126141: Server-Side Request Forgery (SSRF) in GitLab cve.org · Nov 17, 2026
- CVE-2026-101358: Incorrect Authorization in GitLab cve.org · Nov 17, 2026
- CVE-2026-121948: Incorrect Authorization in GitLab cve.org · Nov 17, 2026
- CVE-2026-110990: Insertion of Sensitive Information into Log File in GitLab cve.org · Nov 17, 2026
- CVE-2026-122226: Improper Cleanup on Thrown Exception in GitLab cve.org · Nov 17, 2026
- CVE-2026-110750: Missing Authorization in GitLab cve.org · Nov 17, 2026
More on GitLab
2 other articles, newest first
Edited and approved by Jarosław Krzemiński. Spotted a mistake? Report a correction or read the corrections policy.




Comments