Skip to main content
Mallory
CriticalVulnerability

CVE-2026-1868: Insecure template expansion in GitLab AI Gateway Duo Workflow Service

Published Feb 9, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.9Critical · v3.1
EPSS0.70%54th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
GitLab
IdentifiersCVE-2026-1868CWE-1336 · Improper Neutralization of Special…

CVE-2026-1868 is an insecure template expansion vulnerability in the Duo Workflow Service component of GitLab AI Gateway. Improper handling of user-supplied data in crafted Duo Agent Platform Flow definitions allows an authenticated GitLab user to cause denial of service or execute code on the Gateway. Affected release ranges begin at 18.1.6, 18.2.6, and 18.3.1 and include vulnerable releases through 18.6.1, 18.7.0, and 18.8.0. The vulnerability was fixed in AI Gateway versions 18.6.2, 18.7.1, and 18.8.1.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can disrupt GitLab AI Gateway availability through denial of service or permit code execution on the Gateway. The execution privilege level and any resulting access to other systems are not specified.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by restricting access to authenticated GitLab accounts that can define or modify Duo Agent Platform Flow content, limiting use of self-hosted AI Gateway workflow features to trusted administrators and users, and monitoring for abnormal workflow submissions or Gateway instability. Because exploitation requires authenticated access and targets template processing of crafted flow definitions, minimizing who can supply such definitions can reduce risk until upgrades are completed.

Remediation

Patch, then assume compromise.

Upgrade affected self-hosted GitLab AI Gateway deployments to a fixed release: 18.6.2, 18.7.1, or 18.8.1, according to the applicable release line. GitLab released these fixes on February 6, 2026 and recommended immediate upgrades. GitLab-hosted AI Gateways were already patched; GitLab.com, GitLab Dedicated, and self-managed customers using GitLab-hosted gateways do not need to take action for this vulnerability.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GitLabAi-Gatewayapplication
FAQ

Frequently asked questions

Is CVE-2026-1868 exploited in the wild?
As of Oct 5, 2026, Mallory has no reports of CVE-2026-1868 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-1868?
As of Oct 5, 2026, Mallory has found no public exploit for CVE-2026-1868.
Is there a patch for CVE-2026-1868?
Upgrade affected self-hosted GitLab AI Gateway deployments to a fixed release: 18.6.2, 18.7.1, or 18.8.1, according to the applicable release line. GitLab released these fixes on February 6, 2026 and recommended immediate upgrades.
What products are affected by CVE-2026-1868?
GitLab Ai-Gateway.
How severe is CVE-2026-1868?
CVE-2026-1868 has a CVSS v3.1 score of 9.9 (Critical) and an EPSS score of 0.70% (54th percentile) as of Oct 5, 2026.
Activity feed

Recent activity

20 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
mkd cirtNews · Oct 5, 2026GitLab ја поправа критичната ранливост 9.9 во AI Gateway, која овозможува извршување команди на самохостирани сервери | MKD-CIRT | Национален центар за одговор на компјутерски инцидентиA previously patched GitLab AI Gateway template-engine vulnerability allowing an authenticated user to cause denial of service or execute code through a crafted flow definition. Rated CVSS 9.9, it is mentioned as historical comparison because it shares the CWE-1336 weakness classification with CVE-2026-90970. The content does not establish that the two vulnerabilities are otherwise connected.Read more ↗thecybersecguruNews · Oct 3, 2026GitLab CVE-2026-90970: Critical AI Gateway RCE Flaw | The CyberSec GuruA previously patched GitLab AI Gateway template-engine vulnerability, reported with a CVSS score of 9.9. Crafted flow definitions could lead to code execution or denial of service. It is mentioned as a historical comparison to CVE-2026-90970; the article states GitLab patched it in February 2026.Read more ↗the hacker newsNews · Oct 2, 2026GitLab Patches Critical 9.9 AI Gateway Flaw Allowing Command Execution on Self-Hosted ServersA previously patched GitLab AI Gateway template-engine vulnerability, rated CVSS 9.9, that an authenticated user could trigger through a crafted flow definition to cause denial of service or code execution. It is mentioned as background because it shares the CWE-1336 weakness class with CVE-2026-90970; the content does not establish a direct relationship between the two flaws.Read more ↗security online infoNews · Feb 8, 2026CVE-2026-1868: Critical GitLab Gateway Flaw (CVSS 9.9) Allows RCEA critical insecure template expansion / template injection-style flaw in GitLab AI Gateway’s Duo Workflow Service that can be triggered by an authenticated user via crafted Duo Agent Platform Flow definitions, leading to denial of service and potentially arbitrary code execution on the AI Gateway.Read more ↗
+1 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity15Community discussion across Reddit, Mastodon, and other social sources.