The essentials
- On 12 October 2026, CERT-FR published advisory CERTFR-2026-AVI-1294: multiple vulnerabilities affect unpatched GitLab CE/EE (19.2.x, 19.3.x, 19.4.x), with risks of remote code execution, confidentiality impact, SSRF, and XSS.
- GitLab released fixes 19.4.2, 19.3.5, and 19.2.8 the same day; 19.3.4 is superseded by 19.3.5 to fix a merge request page bug when the Ona integration is enabled.
- CVE-2026-97229 (Critical, CVSS 10.0): under certain conditions, an unauthenticated user could execute arbitrary code on the server via a crafted regular expression in a CI/CD configuration.
- Other High-severity issues cover CI/CD (pipelines on protected branches, raw file cache poisoning), GraphQL (confidential notes), GitLab Duo Agent (prompt-context injection), and secrets in GitLab Pages logs.
What CERT-FR reports
On 12 October 2026, France’s CERT-FR issued advisory CERTFR-2026-AVI-1294 on multiple vulnerabilities in GitLab Community Edition and Enterprise Edition. The official summary cites remote arbitrary code execution, confidentiality and integrity impact, security policy bypass, SSRF, and XSS. Affected versions include 19.3.x before 19.3.4 (CERT threshold; vendor fix 19.3.5), 19.4.x before 19.4.2, and all 19.2.x before 19.2.8. The agency points to GitLab’s security bulletin for patches.
Vendor fixes: self-managed instances first
GitLab released 19.4.2, 19.3.5, and 19.2.8 for CE and EE on 12 October 2026. The notice recommends immediate upgrade for all self-managed installations. GitLab.com already runs the patched release; GitLab Dedicated customers need no hosting-side action. Teams on 19.3.4 should note a bug on merge request pages when the Ona integration is enabled — fixed in 19.3.5.
Critical RCE and the CI/CD chain
CVE-2026-97229 (Critical, CVSS 10.0): GitLab states that an unauthenticated user could, under certain conditions, execute arbitrary code on the server through a crafted regular expression in a CI/CD configuration, due to insufficient validation in the regex compiler. Beyond that scenario, the 12 October patch addresses several High issues in the CI/CD chain: running pipelines on protected branches without authorization (CVE-2026-16301), cache poisoning on raw repository files that may expose protected environment variables (CVE-2026-14814), and pipeline execution after project transfer (CVE-2026-81839, EE).
On the web and collaboration surface: XSS via syntax highlighting (CVE-2026-92883), reading confidential notes on public projects through GraphQL (CVE-2026-16275), and SSRF during repository import (CVE-2026-5954). On GitLab EE, GitLab Duo Agent Platform is affected by injection into AI instruction context (CVE-2026-96893). GitLab Pages may leave tokens and secrets in logs (CVE-2026-101168).
- Inventory: Omnibus, Helm, or source deployments — exact version, HA mode, shared runners.
- Single target: upgrade at least to 19.4.2, 19.3.5, or 19.2.8 on your supported branch.
- Maintenance window: treat unauthenticated RCE as a P0 patch; plan restart and validation of critical pipelines.
- Runners: after upgrade, rerun a reference pipeline on a protected branch to verify CI/CD authorization.
- Duo / AI agents: if EE with Duo Agent, review agent access policies after patching (CVE-2026-96893).
Sources
This note was drafted with AI tools from the cited sources, then reviewed and published under the responsibility of Jordan FOUASSIER, publication director. We summarise the facts and add our reading; source text and images are not reproduced. An error? Write to contact@aigyrosgroup.com.