Last updated: November 2, 2026 at 1:20 PM UTC
All 957 Vulnerability 399 Breach 144 Threat 407 Defense 7
Tag: gitlab (6 articles)Clear

Critical GitLab regex compiler flaw enables unauthenticated code execution across releases back to version 7.0

GitLab disclosed CVE-2026-110264, rated 10.0, which under certain conditions lets an unauthenticated user run arbitrary code on the server through an integer overflow while compiling a specially crafted regular expression. The flaw sits in Onigmo, the Ruby regex engine GitLab ships, and affects every release from 7.0 through 18.11 and the 19.x branches before their fixes, so it spans roughly twelve years of versions. Only self-managed installations must act; GitLab.com and Dedicated already run patched builds. Fixes are in 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3, and 19.5.1. GitLab reports no exploitation yet.

Check
Upgrade self-managed GitLab to the fixed release for your branch, such as 18.11.13 or 19.5.1, immediately, since GitLab.com and Dedicated are already patched.
Affected
Self-managed GitLab from version 7.0 through the unpatched 18.11 and 19.x builds lets an unauthenticated user run code via a crafted regular expression under certain conditions.
Fix
Apply the fixed GitLab release, restrict who can submit regex-bearing pipeline input where possible, and monitor the server for unexpected code execution.

GitLab patches critical integer overflow in CI/CD regex compiler enabling unauthenticated remote code execution

GitLab disclosed CVE-2026-97229, a critical integer overflow in the CI/CD regular expression compiler that parses and evaluates regular expressions in pipeline configuration files. Under certain conditions, an unauthenticated user can execute arbitrary code on the GitLab server through a specially crafted regular expression. It affects versions from 19.2 before 19.2.8, 19.3 before 19.3.4, and 19.4 before 19.4.2, with fixes in 19.2.8, 19.3.4, and 19.4.2. Self-managed installations must upgrade immediately, while GitLab.com already runs the patched version and Dedicated customers need no action. A researcher reported it through GitLab's HackerOne program, and no exploitation is reported.

Check
Upgrade self-managed GitLab to 19.2.8, 19.3.4, or 19.4.2 immediately, since GitLab.com and Dedicated are already covered and no action is needed there.
Affected
Self-managed GitLab versions before the fixed releases let an unauthenticated user run arbitrary code on the server through a crafted regular expression in pipeline configuration.
Fix
Apply the fixed GitLab releases to self-managed installations, restrict who can submit pipeline configurations, and review the server for unexpected code execution.

Critical GitLab AI Gateway flaw lets authorized users run commands on self-hosted servers

GitLab disclosed a critical flaw in its AI Gateway, the service that connects a GitLab instance to AI models, that could let a logged-in user with Duo Agent Platform access run commands on the gateway under certain conditions. Tracked as CVE-2026-90970 and rated 9.9, it is fixed in gateway versions 19.2.4, 19.3.2, and 19.4.1. Only organizations that host their own gateway need to act; customers using a GitLab-hosted gateway are already fixed. GitLab strongly recommends self-hosted gateway operators update immediately and notified them before publishing. CISA's record currently lists exploitation as none.

Check
Determine whether your organization runs a self-hosted GitLab AI Gateway, and if so upgrade to 19.2.4, 19.3.2, or 19.4.1 immediately.
Affected
Self-hosted GitLab AI Gateways on affected versions let a logged-in user with Duo Agent Platform access run commands on the gateway server under certain conditions.
Fix
Update self-hosted gateways to the fixed versions, limit Duo Agent Platform access to trusted users, and monitor the gateway host for unexpected command execution.

Critical GitLab flaw lets one request read any file from self-hosted servers

CISA warned that attackers are exploiting a critical flaw in self-managed GitLab servers, adding it to its exploited-vulnerabilities catalog with a forensic-triage requirement. Tracked as CVE-2026-85706 and scored 10.0, it is a path-traversal bug in GitLab's repository commits API caused by improper path confinement and missing authentication, letting an unauthenticated attacker read any file on the server with a single crafted request. Exposed files can include SSH keys, database credentials, deploy tokens, CI/CD variables, and source code. GitLab patched it on September 10, and researchers observed in-the-wild probing within about a day. GitLab.com is unaffected; the risk is concentrated on the many self-managed instances organizations run.

Check
Upgrade self-managed GitLab to 19.1.8, 19.2.6, 19.3.2, or later immediately, then rotate secrets the server could expose, including access tokens, deploy tokens, CI/CD variables, SSH keys, and cloud credentials.
Affected
Organizations running self-managed GitLab CE or EE from 18.7 up to the patched releases (CVE-2026-85706); an unauthenticated attacker can read arbitrary files, including secrets and source, in one request.
Fix
Patch now, rotate all potentially exposed secrets, review commits-API and web-server logs for unauthenticated requests with traversal patterns and unusual file access, and treat exposed unpatched instances as possibly already breached.

Critical GitLab flaw lets unauthenticated attackers delete public projects and data

GitLab shipped an out-of-band critical patch for a flaw that lets an unauthenticated attacker remotely modify or delete public projects and user data through a GraphQL directive. Tracked as CVE-2026-19478 and scored 9.4, it affects self-managed Community and Enterprise installations; GitLab.com and Dedicated are already fixed. The company released it outside its normal twice-monthly schedule, and the fixed versions are 19.2.4, 19.1.6, 19.0.8, and 18.11.11, with the 18.2 through 18.10 branches left in the affected range and needing an upgrade. A second, lower-severity GraphQL flaw involving cross-site request forgery was fixed in the same release. GitLab reports no known exploitation yet.

Check
Upgrade self-managed GitLab to a fixed release immediately, and if you run a version between 18.2 and 18.10, plan an upgrade since those branches did not receive a backported fix.
Affected
Organizations running self-managed GitLab Community or Enterprise Edition (CVE-2026-19478); an unauthenticated attacker can remotely modify or delete public projects and user data through a GraphQL directive.
Fix
Apply the out-of-band patch now, prioritize internet-reachable instances, review logs for unexpected GraphQL activity and project or user changes, and restore any affected projects from backups if tampering is found.

Public exploit runs commands as git on unpatched self-managed GitLab servers

A researcher at depthfirst published a working exploit on July 24 for a GitLab flaw patched on June 10, running commands as the git user on any self-managed 18.11.3 server that has not updated. Any authenticated user who can push to a project can trigger it: the attacker commits a crafted Jupyter notebook and opens its commit diff to leak a heap pointer, repeats until an automated probe locates libraries in memory, then fires the payload with two more notebooks. No administrator rights, runner access, or victim interaction are needed. The bug sits in the notebook renderer, which passes repository-controlled data to a parser inside a long-lived worker.

Check
Move self-managed GitLab to a supported release containing the June fix, and for Helm or Operator deployments verify the GitLab version inside the Webservice image rather than only the chart version.
Affected
Self-managed GitLab servers on 18.11.3 or other unpatched builds; any authenticated user able to push a project can run commands as the git service account, with public exploit code now available.
Fix
Upgrade to a fixed release, since no workaround is offered, and note GitLab did not classify the fix as a security issue, so track upstream library bumps rather than security advisories alone.