CWE-1336Weakness · CWE-1336

CVE-2026-1868

CRITICAL · 9.9 CVSS v3.1 Published 2026-02-09

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable Zero-click

Official description

NVD · unedited

GitLab has remediated a vulnerability in the Duo Workflow Service component of GitLab AI Gateway affecting all versions of the AI Gateway from 18.1.6, 18.2.6, 18.3.1 to 18.6.1, 18.7.0, and 18.8.0 in which AI Gateway was vulnerable to insecure template expansion of user supplied data via crafted Duo Agent Platform Flow definitions. This vulnerability could be used to cause Denial of Service or gain code execution on the Gateway. This has been fixed in versions 18.6.2, 18.7.1, and 18.8.1 of the GitLab AI Gateway.

Technical summary

dbcve analysis · high confidence

The GitLab AI Gateway's Duo Workflow Service component contains an insecure template expansion vulnerability. User-supplied data in Duo Agent Platform Flow definitions is not properly sanitized before template processing, allowing injection of malicious template content. This template injection can be exploited to cause Denial of Service or achieve arbitrary code execution on the affected Gateway.

MitigationUpgrade GitLab AI Gateway to versions 18.6.2, 18.7.1, or 18.8.1. If immediate patching is not feasible, restrict network access to the Duo Workflow Service and disable unauthenticated Flow definition processing.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: Low
User interaction: None
Scope: Changed
Confidentiality: High
Integrity: High
Availability: High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Confirm GitLab AI Gateway installation

Locate the AI Gateway service/process. Check for /opt/gitlab-ai-gateway directory, gitlab-ai-gateway service/process, or the presence of AI Gateway in GitLab admin area.

Affected if GitLab AI Gateway is not installed or not present in the environment.
Identify installed AI Gateway version

Run 'gitlab-ai-gateway --version' or check the version file in the installation directory. If using GitLab Omnibus, run 'gitlab-ctl ai-gateway --version'. Compare against the fixed versions: 18.6.2, 18.7.1, or 18.8.1.

Affected if The installed version is below 18.6.2, or the version cannot be determined.
Verify Duo Workflow Service is enabled

Check the AI Gateway configuration file (usually in /etc/gitlab/gitlab.rb or /opt/gitlab-ai-gateway/config.yaml) for the duo_workflow_service or ai_gateway_duo_workflow setting. Confirm the service is running via 'gitlab-ctl service-list' or systemctl status.

Affected if Duo Workflow Service is enabled and running.
Check unauthenticated Flow definition processing

Review AI Gateway configuration for settings controlling Flow definition import/processing. Look for flags like 'allow_unauthenticated_flow_import' or similar. Inspect the API endpoints exposed for Flow management.

Affected if Unauthenticated or unauthenticated Flow definition processing is permitted.
Inspect deployed Flow definitions for template injection

Examine any custom Flow definition files or API payloads containing Duo Agent Platform Flow definitions. Look for unusual template syntax like {{, <% , #{, or shell command patterns within data fields that could indicate exploitation attempts.

Affected if Flow definitions contain unexpected template syntax or appear to have been exploited.

If GitLab AI Gateway with Duo Workflow Service is running and the version is below 18.6.2, or if the version cannot be confirmed and the service is enabled, the environment is potentially affected by CVE-2026-1868.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade GitLab AI Gateway to versions 18.6.2, 18.7.1, or 18.8.1. If immediate patching is not feasible, restrict network access to the Duo Workflow Service and disable unauthenticated Flow definition processing.

Recommended fix High confidence

GitLab AI Gateway version 18.6.2, 18.7.1, or 18.8.1 (depending on your current release branch)

Identify the currently running GitLab AI Gateway version using system diagnostics or AI Gateway status commands
Determine the appropriate upgrade target based on your current version branch (18.6.x -> upgrade to 18.6.2, 18.7.x -> upgrade to 18.7.1, 18.8.x -> upgrade to 18.8.1)
Download the corresponding GitLab AI Gateway release from the official GitLab repository or package repository
Stop the AI Gateway service following standard shutdown procedures
Install the upgraded AI Gateway package using the appropriate package manager or installation method
Verify the installation completed successfully and the service starts without errors
Confirm the new version is running: check AI Gateway version information
Test that Duo Workflow Service functions normally with the upgrade

Caveat Review GitLab AI Gateway release notes for any breaking changes between your current version and the target fixed version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation3.0 h
Testing3.0 h
Review / QA2.0 h

10.0 hours of engineering $1,750

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-1868 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1868 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-1868?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsA vendor remedy is published

Severity 9.9 Critical

Exploit likelihood EPSS, next 30 days 0.5%

Remediation

A high-priority fix

Have this fixed 10 hrs · High

Typical engagement from $1,750

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-1868 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References