Halloween DealsAmazon USHalloween week deals: useful picks before month-endAmazon US: current deals, useful picks and tech finds.Check DealsSlow PC?RecommendedPC slow today? Run a repair scan before it gets worseResolve common Windows issues and optimize system performance.Scan NowHalloween DealsAmazon USOctober picks are moving - compare before checkoutAmazon US: current deals, useful picks and tech finds.See Picks×
FREEDOM251

Freedom251 › Blog › AI Gateway

GitLab Warns of Critical RCE Risk in AI Gateway: Who Needs to Patch

By Freedom251 Team · · 3 min read

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Organizations running a self-hosted GitLab AI Gateway should check their version and upgrade if it is affected. GitLab’s February 6, 2026 security advisory documents a critical template-expansion vulnerability in the Duo Workflow Service, tracked by GitLab as CVE-2026-1868 and rated CVSS 9.9. A separate report attributes the issue to CVE-2026-90970, but that identifier is not confirmed by the matching GitLab advisory.

What is the GitLab AI Gateway vulnerability?

The documented weakness is insecure expansion of user-controlled template data in the Duo Workflow Service. A specially crafted Duo Agent Platform Flow definition could cross the intended template boundary and cause denial of service or code execution on the AI Gateway, according to GitLab’s February 6, 2026 advisory and its CVE record.

As an Amazon Associate I earn from qualifying purchases.

The reported attack requires access to Duo Agent Platform functionality; it is not described as an unauthenticated attack available to anyone on the internet. The relevant exposure question is whether users who can create or modify Flow definitions can submit crafted content to an affected gateway.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Why the CVE number needs care

BleepingComputer identifies the reported RCE as CVE-2026-90970. GitLab’s official advisory for the closely matching insecure-template-expansion issue identifies it as CVE-2026-1868. The official CVSS 9.9 rating applies to CVE-2026-1868; it should not be attributed to CVE-2026-90970 unless GitLab publishes an advisory directly confirming that link.

This distinction matters when searching vulnerability scanners, incident records, and vendor notices: use GitLab’s advisory and fixed-version guidance for remediation, and treat the reported CVE-2026-90970 attribution as unconfirmed by that advisory.

Which AI Gateway versions are affected or fixed?

GitLab says the critical fix is included in AI Gateway versions 18.6.2, 18.7.1, and 18.8.1. Its advisory describes affected branches beginning at 18.1.6, 18.2.6, and 18.3.1 and running before the corresponding fixed releases. Because those branch references do not map one-to-one to the three fixed-version numbers in the summary, administrators should use GitLab’s version-specific advisory and upgrade guidance rather than infer safety from a branch number alone.

AI Gateway release What GitLab’s advisory says
18.6.2 Includes the critical fix
18.7.1 Includes the critical fix
18.8.1 Includes the critical fix

Upgrade to the fixed release that applies to your installation, or a later release that GitLab documents as containing the fix. Do not assume an installation is protected merely because it is on a newer-looking version string; verify the exact AI Gateway version against GitLab’s update instructions.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Who needs to take action?

Self-hosted AI Gateway

Prioritize GitLab Duo Self-Hosted installations and other deployments where your organization operates the AI Gateway. Inventory each gateway and confirm its version, whether Duo Agent Platform is enabled, and which users can author or change Flow definitions. GitLab strongly recommends prompt upgrades for affected Duo Self-Hosted installations.

GitLab-hosted AI Gateway

GitLab says it deployed a fix to its hosted AI Gateway for the February advisory. GitLab.com, GitLab Dedicated, and GitLab Self-Managed customers using the GitLab-hosted gateway did not need to take action for that advisory. The key distinction is the gateway mode in use, not simply whether GitLab Self-Managed is deployed.

GitLab Dedicated

Dedicated is a single-tenant deployment option, and GitLab’s deployment guidance says its AI Gateway can keep processing in the selected region. That does not, by itself, establish whether a particular customer operates a self-hosted gateway or uses GitLab’s hosted service. Confirm the configuration with the organization’s administrator before deciding that no patch action is required.

What should administrators do?

  1. Inventory deployments. List each AI Gateway and record whether it is self-hosted, GitLab-hosted, or part of a Dedicated configuration.
  2. Check the installed version. Compare each self-hosted instance with the applicable fixed release—18.6.2, 18.7.1, or 18.8.1—or a later release that GitLab confirms includes the fix.
  3. Upgrade affected instances. Follow GitLab’s Duo Self-Hosted update procedure for the deployment. Schedule and verify the gateway update rather than relying on an assumed update of the broader GitLab installation.
  4. Review access to Flow definitions. Check who can create or modify Duo Agent Platform Flows, whether service accounts have more privileges than needed, and whether those permissions remain appropriate.
  5. Check activity and preserve evidence. Retain relevant logs and investigate unusual Flow changes or unexpected command activity on the gateway. Avoid destroying logs during remediation if an incident may need investigation.
  6. Record verification. Confirm the post-upgrade AI Gateway version and document the change for incident response and audit records.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

What is known about exploitation?

No reliable public count of vulnerable installations or affected customers is available, and no verified public evidence of active exploitation or a public proof of concept was identified. Those gaps do not reduce the urgency of upgrading an exposed, affected self-hosted gateway: the officially documented issue permits code execution under its stated conditions and carries a CVSS 9.9 rating.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

AI GatewaycybersecurityGitLabGitLab Duovulnerability management

Leave a Reply

Your email address will not be published. Required fields are marked *

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Recommended PC Tool
Recommended PC Tool
Crashes, No Sound, or Screen Glitches?Free driver scan
Windows Errors? Fix Them Before They SpreadFree repair scan

Two free Windows tools

One Free Minute Could Fix That PC

Before you go - each of these free tools takes about a minute and tackles what quietly slows a Windows PC down.

Special offer. View Outbyte info, uninstall instructions, EULA, and Privacy Policy.