Skip to navigation

Threat reportVulnerabilityTL-2026-2846

GitLab AI Gateway critical RCE via prompt template sandbox escape (CVE-2026-90970)

criticalPATCHED

GitLab patched a critical (CVSS 9.9) flaw in the self-hosted AI Gateway that lets an authenticated user with Duo Agent Platform access escape the prompt template sandbox through a crafted flow configuration and run arbitrary commands on the gateway. Fixed in AI Gateway 19.2.4, 19.3.2 and 19.4.1; no active exploitation or public PoC has been reported.

Key facts

IdentifiersTL-2026-2846, CVE-2026-90970, CVE-2026-1868
SeverityCRITICAL
CVSS9.9 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H)
EPSSCVE-2026-90970: 0.9% (59.8th percentile); CVE-2026-1868: 0.5% (46.1th percentile)
Affected productsGitLab AI Gateway (Self-Managed Self-Hosted)
Weaknesses (CWE)CWE-1336
MITRE ATT&CK techniquesT1059 Command and Scripting Interpreter, T1068 Exploitation for Privilege Escalation, T1078 Valid Accounts, T1190 Exploit Public-Facing Application, T1552 Unsecured Credentials, T1552.004 Unsecured Credentials: Private Keys
MotivationUNKNOWN
Target sectorstechnology, software-development, enterprise
Target regionsGlobal
Detection rules9 (1 shown free)
Sources10 cited sources

Detection coverage

As of 2026-10-03, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-2846 across Splunk SPL, Microsoft KQL and Sigma, covering 17 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Unexpected Child Process of AI Gateway Service (CVE-2026-90970) - Post-Exploitation

Detects a shell, network client, interpreter or recon utility spawned directly by the Python/uvicorn/gunicorn process hosting the GitLab AI Gateway. Arbitrary command execution after the prompt template sandbox escape surfaces as exactly this parent-child relationship, which GitLab's remediation guidance names as the process telemetry to monitor. Root-owned children are flagged because they indicate the gateway is running with excess privilege.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1059, T1059.004, T1059.006
  • Data sources: sysmon_for_linux, DeviceProcessEvents, linux_process_creation
  • Severity: critical
  • Confidence: high

Splunk SPL

```CVE-2026-90970 - unexpected child process of the AI Gateway service (command execution after sandbox escape)```
index=linux sourcetype="sysmon:linux" EventCode=1 (host="*ai-gateway*" OR host="*aigw*")
| regex ParentImage="(?i)/(python[0-9.]*|uvicorn|gunicorn)$"
| regex Image="(?i)/(sh|bash|dash|zsh|ash|busybox|env|curl|wget|nc|ncat|netcat|socat|perl|ruby|php|node|openssl|base64|chmod|chown|whoami|id|uname|hostname|ifconfig|ip|nslookup|dig|ss|netstat|ps|find|tar|scp|ssh|crontab|sudo|su)$"
| eval privileged=if(User="root" OR User="0", "yes", "no")
| stats count earliest(_time) as first_seen latest(_time) as last_seen values(CommandLine) as command_lines values(ParentCommandLine) as parent_cmdlines by host, User, privileged, ParentImage, Image
| convert ctime(first_seen) ctime(last_seen)
| sort - count

Microsoft KQL

// CVE-2026-90970 - unexpected child process of the AI Gateway service (Defender for Endpoint on Linux)
DeviceProcessEvents
| where Timestamp > ago(24h)
| where DeviceName matches regex '(?i)(ai-gateway|aigw)'
| where InitiatingProcessFileName matches regex '^(python[0-9.]*|uvicorn|gunicorn)$'
| where FileName in~ ('sh', 'bash', 'dash', 'zsh', 'ash', 'busybox', 'curl', 'wget', 'nc', 'ncat', 'netcat', 'socat', 'perl', 'ruby', 'php', 'node', 'openssl', 'base64', 'whoami', 'id', 'uname', 'nslookup', 'dig', 'crontab', 'sudo', 'su')
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessFileName, InitiatingProcessCommandLine, InitiatingProcessParentFileName, ReportId
| order by Timestamp desc

Sigma

title: Suspicious Child Process of GitLab AI Gateway Python Service (CVE-2026-90970)
id: 3fad71a4-85eb-4062-9c49-da15e6fc7034
status: experimental
description: Detects shells, network clients, interpreters and recon utilities spawned directly by a Python, uvicorn or gunicorn process. Scope to the AI Gateway hosts in your backend because the parent match alone is generic. Indicates command execution after the CVE-2026-90970 template sandbox escape.
references:
  - https://nvd.nist.gov/vuln/detail/CVE-2026-90970
  - https://docs.gitlab.com/releases/patches/other-patches/patch-release-gitlab-ai-gateway-19-4-1-released/
author: Threadlinqs Team
date: 2026-10-03
tags:
  - attack.execution
  - attack.t1059.004
  - attack.t1059.006
  - cve.2026.90970
logsource:
  category: process_creation
  product: linux
detection:
  selection_parent:
    ParentImage|re: '(?i)/(python[0-9.]*|uvicorn|gunicorn)$'
  selection_child:
    Image|endswith:
      - '/sh'
      - '/bash'
      - '/dash'
      - '/zsh'
      - '/ash'
      - '/busybox'
      - '/curl'
      - '/wget'
      - '/nc'
      - '/ncat'
      - '/netcat'
      - '/socat'
      - '/perl'
      - '/ruby'
      - '/php'
      - '/openssl'
      - '/whoami'
      - '/nslookup'
      - '/dig'
      - '/crontab'
  condition: selection_parent and selection_child
falsepositives:
  - Container entrypoint or health-check scripts that start through a Python supervisor
  - Administrators running diagnostic commands from a Python-based tool on the gateway host
level: high

Known false positives:

  • Container entrypoint or health-check scripts launched by a Python supervisor
  • Administrators running diagnostics from a Python-based tool on the gateway host

Tuning notes: Run for one week in report mode and allowlist the exact Image plus CommandLine pairs your gateway legitimately spawns. Replace the host filter with your asset tag for AI Gateway nodes. If the gateway runs in a container, make sure the endpoint sensor sees container process events.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • AI Gateway Template Sandbox Probe Error Burst (CVE-2026-90970) - Exploitation · unlock with TL Creds
  • AI Gateway Host Credential and Secret Harvesting by Gateway-Spawned Process (CVE-2026-90970) - Post-Exploitation · unlock with TL Creds
  • AI Gateway Pivot to Cloud Metadata and Secret Stores (CVE-2026-90970) - Lateral Movement · unlock with TL Creds
  • Template Sandbox-Escape Expression in Requests to AI Gateway Ingress (CVE-2026-90970) - Exploitation · unlock with TL Creds
  • Reverse Shell or Download-and-Execute from AI Gateway Process (CVE-2026-90970) - Post-Exploitation · unlock with TL Creds
  • Shell or Netcat-Class Tool Outbound Connection on AI Gateway Host (CVE-2026-90970) - C2 · unlock with TL Creds
  • AI Gateway Template Sandbox-Escape Expression in Application Logs (CVE-2026-90970) - Exploitation · unlock with TL Creds
  • AI Gateway Egress to Destinations Outside LLM-Provider Baseline (CVE-2026-90970) - C2 / Egress · unlock with TL Creds

Indicators of compromise

As of 2026-10-03, Threadlinqs Intelligence tracks 17 indicators of compromise for TL-2026-2846.

17 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

CVE-2026-90970 is an improper neutralization weakness (CWE-1336) in the custom flow prompt template handling of the GitLab AI Gateway, the service that brokers GitLab Duo / Duo Agent Platform requests to LLM back ends in Self-Managed Self-Hosted deployments. Per GitLab's advisory ("Improper Neutralization issue in custom flow prompt template impacts AI Gateway") and the NVD record, an authenticated user with Duo Agent Platform access could escape the prompt template sandbox via a specially crafted flow configuration, resulting in arbitrary command execution on the AI Gateway.

The CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H (9.9). Network-reachable, low complexity, low privileges and no user interaction are required. Scope is changed, reflecting that code execution in the gateway crosses the sandbox boundary and impacts resources beyond the template engine. Affected versions are AI Gateway 18.1.6 through 19.2.3, 19.3.0 through 19.3.1 and 19.4.0. Fixed versions are 19.2.4, 19.3.2 and 19.4.1. GitLab-hosted environments (GitLab.com, Dedicated, and Self-Managed instances using the GitLab-hosted gateway) are already protected and need no action; only self-hosted AI Gateway installations must upgrade following the official Self-Hosted AI Gateway documentation. The issue was reported through HackerOne by researcher invisiblemeerkat. GitLab conducted targeted outreach to affected customers before disclosure, and BleepingComputer reports no active exploitation, no public PoC and no attribution.

This is the second critical template-sandbox class issue in the same component in 2026. CVE-2026-1868 (also CVSS 9.9, same vector, fixed February 6, 2026 in AI Gateway 18.6.2, 18.7.1 and 18.8.1; found internally by GitLab's Joern Schneeweisz) described insecure template expansion of user-supplied data via crafted Duo Agent Platform Flow definitions in the Duo Workflow Service, enabling denial of service or code execution on the gateway. GitLab also remediated separate AI Gateway flaws involving crafted inline flow configuration overriding the HTTP Host header to redirect model requests and expose cloud credentials. Because the AI Gateway typically holds LLM provider credentials and signing material, command execution on it should be treated as a pivot point into connected cloud and model-provider accounts.

Separate from this flaw, GitLab core had a different, unauthenticated issue in September 2026: CVE-2026-85706, a CVSS 10.0 path traversal / authentication bypass in the repository commits API of GitLab CE/EE, added to CISA KEV on 2026-09-11 with public PoCs within hours. BleepingComputer cites it for context; it is not the same vulnerability and CVE-2026-90970 itself has no reported exploitation. No IOCs have been published; defenders should rely on version inventory, review of Duo Agent Platform flow definitions, and process/egress telemetry on the gateway host.

MITRE ATT&CK techniques by tactic:

Execution

T1059 Command and Scripting Interpreter

Privilege Escalation

T1068 Exploitation for Privilege Escalation; T1078 Valid Accounts

Initial Access

T1078 Valid Accounts; T1190 Exploit Public-Facing Application

Credential Access

T1552 Unsecured Credentials; T1552.004 Unsecured Credentials: Private Keys

Remediation

Patches

  • GitLab AI Gateway 19.2.4
  • GitLab AI Gateway 19.3.2
  • GitLab AI Gateway 19.4.1

Immediate actions

  • Upgrade self-hosted GitLab AI Gateway to 19.2.4, 19.3.2 or 19.4.1 (or later)
  • Restrict Duo Agent Platform access to trusted users until patched
  • Review custom flow configurations and prompt templates for unexpected template expressions

Workarounds

  • No workaround published; GitLab-hosted AI Gateway (GitLab.com, Dedicated, GitLab-hosted gateway for Self-Managed) is already remediated

Longer-term hardening

  • Run the AI Gateway with least privilege, in an isolated network segment with restricted egress
  • Store LLM provider credentials in a secrets manager and rotate them if gateway compromise is suspected
  • Monitor child-process creation and outbound connections from the AI Gateway service

Affected and fixed versions

  • GitLab β€” AI Gateway (Self-Managed Self-Hosted)
    Vulnerable versions: 18.1.6 through 19.2.3; 19.3.0 through 19.3.1; 19.4.0
    Fixed in: 19.2.4; 19.3.2; 19.4.1

Timeline

Last updated · revalidated 1× · latest source

  • GitLab releases AI Gateway 18.6.2, 18.7.1 and 18.8.1 fixing CVE-2026-1868 (CVSS 9.9), insecure template expansion via crafted Duo Agent Platform Flow definitions, the same attack surface later hit by CVE-2026-90970. Found internally by Joern Schneeweisz.
  • Canadian Centre for Cyber Security publishes advisory AV26-103 urging upgrade of Duo Self-Hosted AI Gateway for the earlier critical flaw.
  • CVE-2026-19889 (CVSS 8.2 SSRF via crafted model metadata, AI Gateway 18.9.0-19.2.2, CWE-918) published, exposing Google Vertex AI or AWS Bedrock credentials.
  • CVE-2026-75871 (CVSS 8.2 SSRF via crafted inline flow configuration in AI Gateway, CWE-918) published; a separate flaw in the same flow-handling attack surface.
  • Unrelated GitLab core flaw CVE-2026-85706 (CVSS 10.0 unauthenticated path traversal, CE/EE) added to CISA KEV on disclosure day, with public PoCs within hours; cited by BleepingComputer as context for GitLab's exploitation history.
  • GitLab releases critical core patch 19.4.1, 19.3.3, 19.2.7 for CE/EE (separate from the AI Gateway release).
  • The Hacker News reports the flaw, noting the gateway holds JWT signing keys, that no fix is provided below 18.1.6, and that Docker and Helm deployments must be updated; no known exploitation or public PoC.
  • BleepingComputer reports GitLab warning of the critical AI Gateway RCE; GitLab-hosted instances already protected, GitLab did targeted customer outreach, no active exploitation reported.
  • CVE-2026-90970 published in NVD (CVSS 9.9, CWE-1336) with GitLab AI Gateway patch release 19.4.1 / 19.3.2 / 19.2.4; reporter credited as invisiblemeerkat via HackerOne.

Update history

Sources cited

Previous and next in vulnerability

Drafted by the Threadlinqs research pipeline from 10 sources; published ; last updated .

Threadlinqs Intelligence β€” Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats