Vulnerabilities · 5h ago

GitLab code-execution flaw reaches back to version 7.0

GitLab fixed 12 vulnerabilities in Community and Enterprise editions on October 21, including a critical unauthenticated code-execution flaw affecting releases dating to version 7.0, CERT-EU reported. The release also addresses two high-severity issues involving account takeover under specific SAML/LDAP settings and OAuth/OIDC discovery-cache poisoning.

The critical bug is an integer overflow—a number exceeding the range its storage can hold—while GitLab compiles a specially crafted regular expression. Under certain conditions, that parsing failure lets an unauthenticated attacker run code on the server. GitLab published detection rules for exploitation attempts, but installing a fix cannot establish whether an instance was already compromised.

For organizations running self-managed GitLab, especially on older branches, the flaw’s reach means current-branch inventories can miss exposure: each branch has its own corrected release. If a server was internet-facing, an upgrade closes the flaw but leaves open whether an attacker got in and affected the code and collaboration environment it hosts.

CVE-2026-110264

NVD KEV

CVSS 10 CRITICAL: an issue has been discovered in GitLab CE/EE affecting all versions from 7.0 before 18.11.13, 19.0 before 19.0.10…

Timeline

Sources

8 sources covering this story

Entities

Part of the PlainSec briefing for 2026-10-22

Editions

Related stories