Critical · published February 9, 2026
🔥 GitLab's Duo Workflow Service is vulnerable, and it's a big deal! A crafty user-supplied data entry could lead to a Denial of Service or even allow for code execution on the Gateway! ⚠️ Think of the AI Gateway as a high-tech restaurant kitchen. If a chef (or an attacker) sends in a recipe that the kitchen isn’t equipped to handle, it could cause chaos—like a dish that overflows the pot or even sets the place on fire! An attacker could unleash a wave of chaos, effectively shutting down the AI Gateway or executing arbitrary code, leading to potential data leaks or complete service disruption. This could be absolutely devastating for any organization relying on GitLab's services!
Think of the AI Gateway as a high-tech restaurant kitchen. If a chef (or an attacker) sends in a recipe that the kitchen isn’t equipped to handle, it could cause chaos—like a dish that overflows the pot or even sets the place on fire! This vulnerability arises from insecure template expansion in user-supplied data via crafted Duo Agent Platform Flow definitions, allowing for Denial of Service or code execution vulnerabilities. The flaw affects versions 18.1.6, 18.2.6, 18.3.1 to 18.6.1, 18.7.0, and 18.8.0 of the GitLab AI Gateway.
An attacker could unleash a wave of chaos, effectively shutting down the AI Gateway or executing arbitrary code, leading to potential data leaks or complete service disruption. This could be absolutely devastating for any organization relying on GitLab's services! To protect your systems, update to versions 18.6.2, 18.7.1, or 18.8.1 of the GitLab AI Gateway immediately. Review your configurations to ensure that user-supplied data is properly sanitized and validated. Stay vigilant about applying security patches! You’ve got this! With these steps, you'll be safeguarding your AI Gateway like a pro! 🛡️