GitLab fixes 37 vulnerabilities in CE and EE, including SSRF, XSS and denial-of-service flaws
CERT-FR has warned of multiple vulnerabilities in GitLab Community Edition and Enterprise Edition, which the vendor patched on 16 November 2026. Organisations that self-host GitLab on the 19.3, 19.4 or 19.5 branches are affected.
What to do now
- Product
- GitLab Community Edition (CE) and Enterprise Edition (EE)
- Affected versions
- Versions before 19.3.9, 19.4.x before 19.4.8 and 19.5.x before 19.5.6
- Fixed in
- 19.3.9, 19.4.8 and 19.5.6
- CVE
- CVE-2026-101358
On 17 November 2026, CERT-FR published advisory CERTFR-2026-AVI-1552 on a batch of vulnerabilities in GitLab Community Edition (CE) and Enterprise Edition (EE). The advisory is based on the security bulletin GitLab released the day before. It lists 37 CVE identifiers.
The advisory names several types of risk. An attacker could cause a remote denial of service, gain access to confidential data or bypass the security policy. It also mentions server-side request forgery (SSRF) and cross-site scripting (XSS). CERT-FR does not say which flaw leads to which impact. It also does not describe how the flaws can be exploited, for instance whether an attacker needs to be logged in.
Three release lines are affected: all versions before 19.3.9, 19.4.x versions before 19.4.8, and 19.5.x versions before 19.5.6. Versions 19.3.9, 19.4.8 and 19.5.6 contain the fixes. CERT-FR refers readers to GitLab's own bulletin for full details.
The advisory does not report any active exploitation. Even so, an internet-facing GitLab server is a valuable target. It usually holds source code and CI/CD secrets, and it often has access to other systems. An SSRF flaw, for example, could let an attacker use the GitLab server to reach internal services.
What to do now
- Inventory your self-managed GitLab CE and EE instances and record the exact version each one runs.
- Upgrade to 19.5.6, 19.4.8 or 19.3.9 depending on your branch, following GitLab's security bulletin of 16 November 2026.
- Until you can upgrade, reduce the instance's internet exposure; this is general good practice, not a workaround from the advisory.
- Check GitLab logs for unusual outbound requests or unexpected access to projects.