GitLab patches multiple vulnerabilities across CE/EE
Free public brief. The indicators, the detections with Splunk and KQL already written, and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
CERT-FR advises patching GitLab CE/EE for multiple flaws enabling code execution, data disclosure, and XSS.
CERT-FR published an advisory covering multiple vulnerabilities in GitLab Community Edition (CE) and Enterprise Edition (EE). The flaws affect versions 19.3.x prior to 19.3.3, 19.4.x prior to 19.4.1, and all versions prior to 19.2.7. Collectively, the vulnerabilities could allow an attacker to achieve arbitrary code execution, compromise data confidentiality and integrity, bypass security policies, and conduct remote indirect code injection (cross-site scripting).
Eleven CVEs are referenced in the bulletin (CVE-2026-10518, CVE-2026-4523, CVE-2026-84739, CVE-2026-89078, CVE-2026-8937, CVE-2026-92470, CVE-2026-92529, CVE-2026-92530, CVE-2026-92628, CVE-2026-92874, CVE-2026-93577), tied to GitLab's own security release dated 23 September 2026. No detail is given on individual vulnerability mechanics or exploitation status in this advisory.
Defenders running self-hosted GitLab CE/EE should prioritize upgrading to the fixed versions (19.4.1, 19.3.3, or 19.2.7 and later) referenced in GitLab's official patch release notes. No in-the-wild exploitation is mentioned in this advisory; treat as a routine but timely patch action given the range of impacts including RCE.
Mentioned in this report
Source reporting: https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-1225
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 with the Splunk SPL and Microsoft KQL already written, 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 9,789 reports from 155 sources, 1,534 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