Security AffairsPierluigi Paganini
GitLab AI Gateway Flaw Lets Users Run Commands on Hosts
Part of the CVE-2026-90970 story · since 2 Oct
- Fri 2 Oct, 17:40 UTC. The Hacker News, first report. GitLab Fixes Critical AI Gateway Flaw Enabling Command Execution.
- Fri 2 Oct, 22:22 UTC. SecurityOnline, its first report on the story. GitLab Patches Critical AI Gateway Flaw Enabling Command Execution.
- Sat 3 Oct, 11:46 UTC. Security Affairs, its first report on the story. GitLab AI Gateway Flaw Lets Users Run Commands on Hosts. This article, 3rd of 6.
- Sun 4 Oct, 08:35 UTC. Security Affairs. Security Roundup Exposes CloudSyncD Mac Backdoor and AI Gateway Flaw.
- Tue 13 Oct, 09:12 UTC. The Hacker News. GitLab Patches Critical Flaw That Could Let Attackers Run Server Code.
- Tue 13 Oct, 14:37 UTC. Security Affairs. GitLab patches critical flaw letting attackers run code without logging in.
GitLab has patched a critical vulnerability in its AI Gateway, CVE-2026-90970, rated 9.9 on the CVSS scale. The flaw could allow an authenticated user with access to the Duo Agent Platform to escape the prompt sandbox and execute arbitrary commands on the AI Gateway host. GitLab disclosed the issue on 2 October 2026 and released fixes in AI Gateway versions 19.2.4, 19.3.2 and 19.4.1.
The advisory notes that exploitation would require specific conditions involving a crafted flow configuration, and does not indicate that the vulnerability has been observed in the wild.
The problem lies in how the AI Gateway handles custom flow prompt templates, with the gateway acting as the intermediary between GitLab Duo and underlying AI models. Self-hosted deployments are affected, including installations where the gateway and AI models reside within an organisation’s infrastructure; GitLab states that the issue could grant an attacker foothold into environments handling AI requests and authentication keys.
Affected releases are 18.1.6 through 19.2.3 (fixed in 19.2.4); 19.3.0 through 19.3.1 (fixed in 19.3.2); and 19.4.0 (fixed in 19.4.1). The advisory confirms the issue did not pertain to unauthenticated access, and no proof-of-concept or exploitation details were published. Credit for reporting is given to the HackerOne researcher invisblemeerkat. GitLab notes that customers using GitLab[.]com, GitLab Dedicated, or a GitLab self-managed gateway connected to a GitLab-hosted gateway do not need to take action.
How the story developed
6 articles from 3 outlets since 2 Oct. Quiet since 13 Oct. This was the 3rd report, 18 hours after the first.
- Fri 2 Oct, 17:40 UTC. The Hacker News, first report. GitLab Fixes Critical AI Gateway Flaw Enabling Command Execution.
- Fri 2 Oct, 22:22 UTC. SecurityOnline, its first report on the story. GitLab Patches Critical AI Gateway Flaw Enabling Command Execution.
- Sat 3 Oct, 11:46 UTC. Security Affairs, its first report on the story. GitLab AI Gateway Flaw Lets Users Run Commands on Hosts. This article, 3rd of 6.
- Sun 4 Oct, 08:35 UTC. Security Affairs. Security Roundup Exposes CloudSyncD Mac Backdoor and AI Gateway Flaw.
- Tue 13 Oct, 09:12 UTC. The Hacker News. GitLab Patches Critical Flaw That Could Let Attackers Run Server Code.
- Tue 13 Oct, 14:37 UTC. Security Affairs. GitLab patches critical flaw letting attackers run code without logging in.
- CVE not in KEV
- No CVE
- Larger: an outlet’s first report
- Coverage over time
- Quiet time, folded
Show all 6 articles as a listHide the list
- Fri 2 OctDay 02
- GitLab Fixes Critical AI Gateway Flaw Enabling Command Execution17:40 · The Hacker News · First report
- GitLab Patches Critical AI Gateway Flaw Enabling Command Execution22:22 · SecurityOnline
- Sat 3 OctDay 11
- GitLab AI Gateway Flaw Lets Users Run Commands on Hosts11:46 · Security Affairs · This article, 3rd of 6
- Sun 4 OctDay 21
- Security Roundup Exposes CloudSyncD Mac Backdoor and AI Gateway Flaw08:35 · Security Affairs
Quiet for 9 days
Tue 13 OctDay 112- GitLab Patches Critical Flaw That Could Let Attackers Run Server Code09:12 · The Hacker News · Picked up again
- GitLab patches critical flaw letting attackers run code without logging in14:37 · Security Affairs