GitLab patches 37 flaws in 19.5.6, 19.4.8 and 19.3.9, including wiki and Error Tracking XSS (CVSS 8.7)
Matéria consolidada. Reúne 3 matérias que o Tifon tinha publicado separadamente sobre a mesma história. A IA reescreveu o relatório com o que as 4 fontes trouxeram em 17/11/2026 12:02; os links antigos trazem para cá.
Fontes: cert.cyber.gouv.fr ↗ gbhackers.com ↗ docs.gitlab.com ↗ securityonline.info ↗
GitLab released patch versions 19.5.6, 19.4.8 and 19.3.9 for CE/EE on November 16, 2026. The vendor notice (docs.gitlab.com) and press coverage (securityonline.info, gbhackers.com) count 37 vulnerabilities, while CERT-FR (cert.cyber.gouv.fr) published advisory CERTFR-2026-AVI-1552 on November 17 listing about 45 CVEs. The two most severe are authenticated XSS bugs rated CVSS 8.7: CVE-2026-105739 (wiki pages) and CVE-2026-108153 (Error Tracking). They are followed by CVE-2026-18241 (CVSS 8.2, CI/CD race condition) and CVE-2026-97187 (CVSS 7.6, Kubernetes Secrets exposure). GitLab.com already runs the fix and GitLab Dedicated customers need no action. No source reports exploitation in the wild, and securityonline.info says none of the flaws is in CISA KEV. Self-managed instances should upgrade.
Entenda a falha
A vulnerabilidade
GitLab CE/EE patch releases 19.5.6, 19.4.8 and 19.3.9 (16 November 2026) fix 37 flaws according to the vendor. CERT-FR lists about 45 CVEs. The two most severe are authenticated XSS flaws rated CVSS 8.7: CVE-2026-105739 in wiki pages (from 17.2) and CVE-2026-108153 in Error Tracking (from 16.1). An attacker needs an account, and the victim must view the page. They get JavaScript running in the victim's browser. Next come CVE-2026-18241 (8.2, race condition in CI/CD job authorization, from 9.3, authenticated, high complexity) that exposes protected variables, and CVE-2026-97187 (7.6, workspaces, from 17.6, high privileges) that exposes Kubernetes Secrets from other namespaces. Others are medium or low, such as the GitLab Pages path traversal CVE-2026-11768 and unauthenticated information leaks. Affected: before 19.3.9, 19.4.x before 19.4.8 and 19.5.x before 19.5.6.
Como funciona
In the two XSS flaws, an authenticated user writes content into a wiki page or an Error Tracking page. GitLab stores it and later renders it to anyone who opens the page. Because the input is not properly sanitized, script in that content runs in the viewer's browser, in the context of their GitLab session. In the CI/CD flaw, a pipeline job's access to protected variables and resources is authorized in a way that a race condition can defeat. In the workspaces flaw, the authorization check for clusters connected through the GitLab agent lets a privileged user read Secrets outside their own namespace.
Por que é vulnerável
The XSS flaws come from improper sanitization of user input before it is shown to other users. CVE-2026-18241 is a race condition in pipeline job authorization. CVE-2026-97187 is incorrect authorization in workspaces. Many of the smaller bugs are missing or incorrect authorization checks, or improper input or response validation. The articles do not explain why they went unnoticed or detail what each fix changes.
Como foi descoberta
Per the vendor notice, a0xnirudh reported CVE-2026-105739 through HackerOne, and securityonline.info says the same researcher found both XSS bugs. sunnybounty reported CVE-2026-18241 and maxilagv reported CVE-2026-97187, both via HackerOne. Of the 37 flaws, 21 came through HackerOne and 16 were found internally by GitLab, for example CVE-2026-115428 by Clemens Beck. The fixes shipped in the scheduled patch release, and GitLab publishes the issue details 90 days later. No source reports exploitation, and securityonline.info says none is in CISA KEV.
Explicação gerada por IA a partir da matéria e dos artigos, em 17/11/2026 12:17.
Detalhes técnicos
- CVE-2026-105739: wiki XSS, affecting 17.2 up to the fixed releases. It needs an authenticated attacker and a victim who views the page (AV:N/AC:L/PR:L/UI:R/S:C) (docs.gitlab.com). securityonline.info describes it as stored XSS.
- CVE-2026-108153: Error Tracking XSS, affecting 16.1 and later, with the same CVSS vector (docs.gitlab.com). Both XSS flaws were found by researcher a0xnirudh (securityonline.info).
- CVE-2026-18241 (CVSS 8.2): race condition in pipeline job authorization that exposes protected CI/CD variables and resources. It affects 9.3 and later, requires authentication and has high attack complexity (docs.gitlab.com, gbhackers.com).
- CVE-2026-97187 (CVSS 7.6): an authenticated user with high privileges can read Kubernetes Secrets from other namespaces through workspaces in clusters connected via the GitLab agent. It was reported by maxilagv via HackerOne (gbhackers.com).
- CVE-2026-115428 (CVSS 6.5): NULL pointer dereference in KAS causing DoS, needs a valid agent token (docs.gitlab.com).
- CVE-2026-85778 (CVSS 6.2, EE): code runs in protected pipelines after a scheduled pipeline execution policy is unassigned (docs.gitlab.com).
- CVE-2026-112203 (CVSS 5.9, EE): an upstream Maven repository owner can alter cached packages in a shared virtual registry (docs.gitlab.com, securityonline.info).
- CVE-2026-11768 (CVSS 5.8): path traversal in GitLab Pages exposes other projects' private job artifacts. It affects releases back to 12.4 (gbhackers.com).
- Unauthenticated information leaks (CVSS 5.3): CVE-2026-118961 (private fork commit comments via a public merge request), CVE-2026-121533 (restricted job artifact data) and CVE-2026-16545 (private package metadata) (securityonline.info).
- CVE-2026-123142 (CVSS 4.3): an MCP-scoped OAuth token can make unauthorized issue and merge-request state changes, including approvals and merges (gbhackers.com).
- Other fixes: authorization gaps in Duo, the MCP server, Git LFS, snippets, iterations and imports; an SSRF in repository import; credential exposure in logs via GraphQL; and a group import email spoofing bug (docs.gitlab.com, gbhackers.com).
- Of the 37 flaws, 21 came through HackerOne and 16 were found internally. Thirteen affect EE only, nine touch Duo and one touches the MCP server (securityonline.info). By severity: four high, 24 medium, nine low (gbhackers.com).
- CERT-FR classes the impact as remote denial of service, loss of confidentiality, security policy bypass, SSRF and indirect remote code injection (XSS) (cert.cyber.gouv.fr).
Remediação
- Upgrade self-managed instances (Omnibus, source, Helm) to 19.5.6, 19.4.8 or 19.3.9, or later. Affected: before 19.3.9, 19.4.x before 19.4.8, 19.5.x before 19.5.6 (cert.cyber.gouv.fr).
- The releases include no new migrations, but a default Omnibus upgrade stops and restarts services (gbhackers.com).
- Review who can edit wikis and Error Tracking settings, rotate protected CI/CD variables if misuse is suspected, check Kubernetes agent permissions for workspaces, and limit public projects that fork private code (securityonline.info).
- GitLab publishes issue details 90 days after release.
Relatos divergentes
- Number of CVEs: 37 flaws according to docs.gitlab.com (vendor), securityonline.info and gbhackers.com; about 45 CVE identifiers according to cert.cyber.gouv.fr. The vendor notice is the more authoritative for the count. The CERT-FR gap is unexplained and may reflect how it counts identifiers, but this is not confirmed.
- Scores and prerequisites: CERT-FR gives no CVSS scores or per-flaw prerequisites, so those come from the vendor notice and press.
Linha do tempo
-
CERT-FR: Multiple GitLab CE/EE vulnerabilities (DoS, SSRF, XSS, data disclosure) fixed in 19.3.9, 19.4.8 and 19.5.6
ler a análise desta fonte ocultar
The French CERT (CERT-FR) published advisory CERTFR-2026-AVI-1552 on multiple vulnerabilities in GitLab Community Edition (CE) and Enterprise Edition (EE). According to the advisory, the flaws allow remote denial of service, loss of data confidentiality, security policy bypass, server-side request forgery (SSRF) and indirect remote code injection (XSS). Affected versions are GitLab CE/EE before 19.3.9, 19.4.x before 19.4.8 and 19.5.x before 19.5.6. The advisory refers to the vendor's patch release bulletin of 16 November 2026 and lists about 45 CVE identifiers. It gives no CVSS scores, prerequisites per flaw or exploitation in the wild, and no web research was performed, so those details are not confirmed here.
Remediation
Apply the fixes from the GitLab patch release bulletin: update to GitLab 19.3.9, 19.4.8 or 19.5.6, or later.
-
GitLab patches 37 vulnerabilities in 19.5.6, 19.4.8 and 19.3.9, including CI/CD race condition, Pages path traversal and MCP flaws
ler a análise desta fonte ocultar
GitLab released 19.5.6, 19.4.8 and 19.3.9 on November 16, 2026 for Community and Enterprise Editions. The releases fix 37 vulnerabilities: four high, 24 medium and nine low severity. The article does not report exploitation in the wild. Self-managed administrators are urged to upgrade. GitLab.com is already patched and dedicated customers need no action. This record is based on the article alone, because no research tools were used to check GitLab's advisory.
Technical Details
- CVE-2026-18241 (CVSS 8.2): a race condition in job authorization exposes protected pipeline variables and resources. It requires authentication and has high attack complexity.
- Two XSS flaws (CVSS 8.7 each): authenticated attackers can run JavaScript when a victim views an affected page. Both need user interaction.
- CVE-2026-97187: under specific conditions, a high-privileged authenticated user could read Kubernetes Secrets from other namespaces in clusters connected through the GitLab agent. It was reported by researcher maxilagv via HackerOne.
- CVE-2026-11768 (5.8, medium): path traversal in GitLab Pages lets authenticated users read private CI/CD artifacts of other projects. It affects releases back to 12.4.
- CVE-2026-123142 (4.3): an MCP-scoped OAuth token can be used for unauthorized issue and merge-request state changes, including approvals and merges.
- Other fixes cover package registries, Kubernetes proxy access, Duo governance, repository imports and plaintext credential logging.
Remediation
Upgrade self-managed instances to 19.5.6, 19.4.8 or 19.3.9. The releases include no new migrations, but a default Omnibus upgrade stops and restarts services. GitLab publishes vulnerability details 90 days after patching.
-
GitLab patch releases 19.5.6, 19.4.8, 19.3.9 fix 37 flaws incl. wiki and Error Tracking XSS (CVSS 8.7)
The vendor's own patch notice (docs.gitlab.com) confirms the release and lists the full set of CVEs with CVSS vectors, affected ranges and credits. It also adds CVE-2026-115428 and CVE-2026-85778 as notable fixes and names several reporters.
ler a análise desta fonte ocultar
The vendor's own patch notice (docs.gitlab.com) confirms the release and lists the full set of CVEs with CVSS vectors, affected ranges and credits. It also adds CVE-2026-115428 and CVE-2026-85778 as notable fixes and names several reporters.
GitLab published its official patch release notice on November 16, 2026 for 19.5.6, 19.4.8 and 19.3.9 (CE/EE). The notice lists CVEs fixed in this release. The two most severe are authenticated cross-site scripting bugs rated CVSS 8.7: CVE-2026-105739 (wiki pages) and CVE-2026-108153 (Error Tracking). GitLab.com already runs the patched version, and GitLab Dedicated customers need no action. The notice does not state that any flaw is exploited in the wild. No web research was done, so this record rests only on the vendor notice.
Technical Details
- CVE-2026-105739: wiki XSS, versions 17.2 up to the fixed releases. It needs an authenticated user, and the victim must view the page (AV:N/AC:L/PR:L/UI:R/S:C).
- CVE-2026-108153: Error Tracking XSS, affects 16.1 and later, with the same CVSS vector.
- CVE-2026-18241 (CVSS 8.2): race condition in pipeline job authorization that exposes protected CI/CD variables. Affects 9.3 and later.
- CVE-2026-97187 (CVSS 7.6): workspaces let an authenticated user with high privileges read Kubernetes Secrets from other namespaces.
- CVE-2026-115428 (CVSS 6.5): NULL pointer dereference in KAS (DoS), needs a valid agent token.
- CVE-2026-85778 (CVSS 6.2): code runs in protected pipelines after a scheduled pipeline execution policy is unassigned (EE).
- CVE-2026-112203 (CVSS 5.9): an upstream Maven repository controller can alter cached packages (EE).
- CVE-2026-11768 (CVSS 5.8): path traversal in GitLab Pages exposes private job artifacts.
- Unauthenticated information leaks (CVSS 5.3): CVE-2026-118961, CVE-2026-121533, CVE-2026-16545.
- The remaining fixes are CVSS 5.4 and below: authorization gaps in Duo, the MCP server, Git LFS, snippets, iterations and imports. The list also includes an SSRF in repository import, log exposure of credentials via GraphQL, and a group import email spoofing bug.
- Many were reported via HackerOne, and others were found internally by GitLab staff.
Remediation
- Upgrade self-managed instances to 19.5.6, 19.4.8 or 19.3.9.
- GitLab publishes the issue details 90 days after release.
-
GitLab 19.5.6, 19.4.8 and 19.3.9 patch 37 flaws, including wiki XSS CVE-2026-105739 (CVSS 8.7)
ler a análise desta fonte ocultar
GitLab released patch versions 19.5.6, 19.4.8 and 19.3.9 on November 16, 2026. They fix 37 vulnerabilities in GitLab CE/EE. The two most severe are authenticated stored cross-site scripting bugs rated CVSS 8.7: CVE-2026-105739 in wiki pages and CVE-2026-108153 in Error Tracking pages. GitLab reports no exploitation, and the article says none of the flaws appear in CISA KEV. GitLab.com already runs the fix, and GitLab Dedicated customers need no action. This summary comes only from the article. No web research was done, so the GitLab advisory was not checked.
Technical Details
- The XSS flaws need an authenticated attacker, and the victim must view the page.
- CVE-2026-18241 (CVSS 8.2) is a race condition in pipeline job authorization. It could expose protected CI/CD variables and resources.
- CVE-2026-97187 (CVSS 7.6) lets an authenticated user read Kubernetes Secrets from other namespaces through workspaces in clusters linked by the GitLab agent. It requires high privileges.
- Several unauthenticated medium-severity information leaks score 5.3:
- CVE-2026-118961 exposes private fork commit comments through a public merge request.
- CVE-2026-121533 leaks restricted job artifact data.
- CVE-2026-16545 leaks private package metadata.
- CVE-2026-11768 is a path traversal in GitLab Pages that exposes other projects' private job artifacts.
- CVE-2026-112203 lets an upstream repository owner alter cached Maven packages in a shared virtual registry.
- Nine fixes touch GitLab Duo, and one touches the MCP server.
- Of the 37 flaws, 21 were reported through HackerOne and 16 were found internally. Researcher a0xnirudh found both XSS bugs.
- Thirteen of the fixes affect EE only.
Remediation
- Upgrade self-managed instances (Omnibus, source and Helm) to 19.5.6, 19.4.8 or 19.3.9.
- Review who can edit wikis and Error Tracking settings.
- Rotate protected CI/CD variables if misuse is suspected.
- Check Kubernetes agent permissions for workspaces.
- Limit public projects that fork private code.
- GitLab will publish the issue details 90 days after release.