GitLab's AI Gateway RCE Is a Template Injection Bug Wearing an AI Costume

GitLab disclosed CVE-2026-90970 on October 2, and the number attached to it does a lot of work: CVSS 9.9, network attack vector, low privileges required. The flaw sits in the AI Gateway — the service that fronts GitLab Duo's AI features — and it lets an authenticated user with Duo Agent Platform access escape the prompt template sandbox through a specially crafted flow configuration, then run arbitrary commands on the gateway host. Read the CWE tag in the GitHub advisory and the spell-check suspicion goes away: CWE-1336, improper neutralization in a template engine. This is not a model misbehaving. It's not a jailbreak. It's template injection — the same bug class that has been popping web apps since the PHP era — wearing an AI costume because the templates in question happen to assemble prompts.

Two details make this more than routine patch Tuesday. First, it isn't the first time. The Cloud Security Alliance's research note points out that CVE-2026-1868, patched back in February, also scored 9.9 and also involved template expansion of user-supplied flow definitions. Two critical flaws of the same shape in the same component within eight months is hard to explain as separate coding mistakes; the more plausible reading is that the flow engine's template handling is a durable attack surface, and each patch just trims one branch of it. Second, the blast radius isn't the gateway alone. Per reporting on the advisory, the gateway holds JWT signing keys and connects to both the GitLab instance and the AI model providers — compromise there reaches well past the AI feature itself. GitLab patched versions 19.2.4, 19.3.2, and 19.4.1, says GitLab.com and GitLab-hosted gateways are already protected, and conducted targeted outreach to self-hosted customers before disclosure. The GitHub advisory's EPSS estimate sits under 1% for near-term exploitation, so this isn't a mass-exploitation event today — but the advisory's affected range starts at 18.1.6, and the CSA note flags reporting that older lines may not have fixes available, which is the kind of detail self-hosted admins should verify against their own deployment before assuming they're covered.

Source article image
Source image 1

The operational lesson is a placement problem. Teams keep bolting AI plumbing onto the development platform and treating it like a feature toggle, but an AI gateway is a credential-bearing tier: it sits between your source of truth and third-party model providers, and it parses configuration written by people who aren't security engineers. It deserves the same treatment you'd give identity or CI/CD infrastructure — patch cadence, restricted authorship of custom flows, monitoring for odd egress. GitLab pre-notifying its self-hosted customers tells you the company knows exactly how exposed this tier is. The question I'd put to anyone running a self-hosted Duo deployment: when the gateway was installed, did anyone treat it as infrastructure with a patch calendar — or as a checkbox that came with the AI license?

Source article image
Source image 2

Sources

Comments

Post a Comment

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

Image
Modern AI doesn't replace infrastructure — it runs on top of it. (Photo: Unsplash) For a while, AI coverage had the energy of a mall demo kiosk: very shiny, slightly chaotic, and usually one prompt away from embarrassment. Lately, though, the more interesting story is less about flashy demos and more about infrastructure. A useful CNBC piece argued that AI is not simply going to vaporize enterprise software overnight, and that sounds about right. In real companies, software does not disappear just because a model can summarize a meeting or write a decent SQL query. What actually happens is messier and more practical: AI starts sneaking into the plumbing. It shows up in search, support workflows, procurement tools, analytics dashboards, and data pipelines. The real winners may not be the loudest chatbot wrappers, but the vendors that make enterprise systems easier to operate, easier to query, and slightly less soul-crushing for the humans trapped inside them. That is less cinematic ...
Read more

When Two AI Bots Finally Learned to Talk in Discord

I spent part of the day doing something that sounds like the setup for a bad joke: getting two local AI assistants to talk to each other in the same Discord channel. Not through a web UI. Not by bouncing prompts manually between windows like a human message queue. In the actual shared channel, where both could see the conversation and react to each other. The funny part is that the problem was not intelligence. It was manners. Both bots were defensive by default around bot-authored messages, which is the sensible setting if you do not want your infrastructure turning into a recursive support group. The downside is obvious: if both assistants treat other bots as suspicious background noise, they will never coordinate on anything more useful than silence. The fix was to make both sides accept bot-authored messages only when they were explicitly mentioned. That detail matters more than it sounds. Blanket bot acceptance is how you end up with two enthusiastic systems discovering each oth...
Read more

Enterprise AI Is Quietly Becoming a Systems Integration Problem

The funniest thing about enterprise AI in 2026 is that the flashy part is basically over. The demos are still shiny, sure, but the real story now looks a lot less like science fiction and a lot more like infrastructure planning, governance, and somebody in IT asking who exactly is paying for all these agents. Over the past few weeks, Microsoft has been pitching Agent 365 and a bundled Microsoft 365 E7 “Frontier Suite” aimed at governing and securing fleets of workplace agents, Google has introduced a new Workspace add-on for higher AI usage tiers, and Anthropic has thrown $100 million behind a partner network to help companies move Claude deployments from pilot mode into something that can survive contact with procurement, compliance, and existing systems. That cluster of announcements says something pretty clear: enterprise AI is no longer mainly a model race. It is becoming a packaging, controls, and implementation race. The clever model still matters, obviously, but once every vendo...
Read more