GitLab AI Gateway CVE-2026-90970: How a Prompt Template Can Execute Commands (CVSS 9.9)

By Carlos Montiel | Enterprise AI Specialist
Leer en español →
Published: 2026-10-06 | By: Carlos Montiel | Reading time: ~4 minutes

The gateway connecting your DevOps platform to AI models is an attack surface too: on October 2, GitLab patched a CVSS 9.9 flaw that turns a manipulated flow configuration into command execution.

What we know about CVE-2026-90970

According to The Hacker News, GitLab fixed CVE-2026-90970, a critical vulnerability with a CVSS score of 9.9 in the AI Gateway, the component that routes Duo Agent Platform requests to the models. The flaw lets an authenticated user with access to Duo Agent Platform “escape the prompt template sandbox through a specially crafted flow configuration” and achieve arbitrary command execution on the gateway. The report came in through HackerOne from a researcher identified as “invisiblemeerkat.”

CVE: CVE-2026-90970 CVSS: 9.9 (critical) Component: GitLab AI Gateway (Duo Agent Platform) Requirement: authenticated user with access to Duo Agent Platform Vulnerable: 18.1.6 up to (not including) 19.2.4 / 19.3.2 / 19.4.1 Fixed in: 19.2.4, 19.3.2, and 19.4.1 Exploitation: "none" per CISA's assessment (Oct 2, 2026)

How it works: template injection, not “AI magic”

The CVE record classifies the weakness as CWE-1336 (improper neutralization of special elements used in a template engine). Put simply: the gateway builds prompts from templates that are rendered inside a sandbox. If whoever controls the flow configuration can slip in expressions the sandbox doesn’t block, those expressions run with the gateway process’s permissions, not the user’s. It’s the same class of bug as web template engines from years ago, now inside agent infrastructure.

One relevant detail The Hacker News points out: in February, CVE-2026-1868 had been fixed, also CVSS 9.9 and also a template-engine weakness in the same component. This time’s advisories don’t mention the earlier flaw. Two critical issues of the same family in eight months suggest the template sandbox is a priority area for review.

Who needs to act

GitLab says customers on GitLab.com, GitLab Dedicated, and self-managed instances that use a GitLab-hosted gateway don’t need to do anything: it’s already fixed. Only those running a self-hosted AI Gateway need to upgrade to 19.2.4, 19.3.2, or 19.4.1, depending on their branch.

Risk: the attacker is already an authenticated user, so the realistic scenario is an employee, contractor, or compromised account using the agent flow to go from “Duo user” to “commands on the gateway server,” where model API keys and internal network access tend to live.

What this means for a company using AI

For your team: (1) inventory whether you run a self-hosted AI Gateway and which version it’s on; (2) treat AI components as production services with a patching window, not as “developer tools”; (3) restrict who can edit agent flow configurations: that configuration is, in practice, code; (4) store model keys with the narrowest possible scope, because a compromised gateway exposes all of them. CISA sees no exploitation as of October 2, but the window between patch and attack is usually short.
Carlos Montiel
Enterprise AI Solutions Architect
Specialist in LLMs, Agents, and Orchestration
guatemalia.com/#contacto · info@guatemalia.com

Need to implement AI in your company?

Carlos Montiel is an enterprise AI solutions architect. He implements LLMs, Agents, RAG, and orchestrators for companies across Guatemala and Latin America. Reach out for a consultation.

Contact Carlos Montiel

info@guatemalia.com