GitLab patches critical CI/CD RCE flaw
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
GitLab fixed 24 vulnerabilities including a CVSS 10.0 unauthenticated RCE via malicious CI/CD config; no in-the-wild exploitation reported.
NCSC-NL issued an advisory summarizing GitLab's remediation of 24 vulnerabilities across GitLab Community Edition (CE) and Enterprise Edition (EE), affecting versions prior to 19.2.8, 19.3.5, and 19.4.2. The flaws span multiple components including the CI/CD pipeline environment, authorization mechanisms, the API, Kubernetes integration, and the package registry. Weakness classes include XSS, SSRF, open redirect, race conditions, incorrect authorization, sensitive data logging, integer overflow, and improper neutralization of LLM prompt input.
The most severe issue, CVE-2026-97229, carries a maximum CVSS 3.1 score of 10.0 and allows an unauthenticated attacker to execute arbitrary code via a malicious CI/CD configuration. Several other high-severity flaws (CVE-2026-92883, CVE-2026-16301, CVE-2026-14814) could enable unauthorized access to sensitive data or privilege abuse. No exploitation in the wild is mentioned in this advisory.
GitLab has released fixed versions 19.2.8, 19.3.5, and 19.4.2 addressing all listed CVEs. NCSC-NL recommends that organizations running affected GitLab CE/EE instances apply these updates promptly given the breadth and severity of the issues, particularly the unauthenticated RCE vector.
Mentioned in this report
Source reporting: https://advisories.ncsc.nl/2026/ncsc-2026-0414.html
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,854 reports from 146 sources, 616 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs