What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
First determine whether your deployment uses a GitLab-hosted or self-hosted AI Gateway. GitLab says it has already patched its hosted gateways, so customers using those gateways—including GitLab.com, GitLab Dedicated, and Self-Managed instances configured to use the hosted service—do not need to take action for CVE-2026-90970. Operators of a self-hosted AI Gateway should check that gateway’s running version or deployed image against GitLab’s affected ranges and upgrade if necessary.
What the vulnerability affects
CVE-2026-90970 is an improper-neutralization issue in a custom flow prompt template in GitLab AI Gateway. Under specified conditions, an authenticated user with Duo Agent Platform access could use a specially crafted flow configuration to escape the prompt-template sandbox and execute arbitrary commands on the AI Gateway. GitLab rates the issue Critical, with a CVSS v3.1 score of 9.9. The affected component is the AI Gateway, which may be deployed separately from the main GitLab application.
As an Amazon Associate I earn from qualifying purchases.
Read GitLab’s October 2026 AI Gateway critical patch release for the advisory and release details.
Recommended Free Tools
Check whether your gateway is GitLab-hosted or self-hosted
Identify the gateway used by the GitLab deployment in question; do not assume that every Self-Managed instance runs its own gateway. GitLab states that it deployed the fix to GitLab-hosted AI Gateways. A deployment using that hosted service is covered by GitLab’s fix. A customer-operated, self-hosted gateway needs to be checked and updated by its operator.
#1 Best Overall
- Made in USA - Proudly produced in Ohio by a Veteran-owned business
- Comprehensive Coverage: This BookFactory log book includes essential fields such as post/shift, time of change, date, weather conditions, and a designated space for detailed notes. This ensures that all relevant information is captured and easily accessible.
- Sturdy Cover: The trans-lux cover protects the log book from wear and tear, ensuring its longevity and maintaining the integrity of your recorded data.
- Essential Security Tool: This log book is an indispensable tool for any organization that values security and accountability. It helps to prevent misunderstandings, improve communication, and ensure a smooth transition between shifts.
- Wire-O with Trans-lux cover, 100 Pages, Dimensions 8.5" x 11" - (Security-Pass-Down) Reorder SKU: LOG-100-7CW-PP(Security-Pass-Down)
For self-hosted deployments, use the installation method’s deployment configuration and runtime information to identify the actual gateway instance and image. The main GitLab application version is not a reliable substitute: the gateway is a separate component and can have its own version and update schedule. GitLab’s AI Gateway installation documentation describes installation and image updates.
Compare the running gateway version with the affected ranges
For each self-hosted AI Gateway, compare the version actually running—not just the version specified in source control—with these ranges from GitLab’s advisory:
| AI Gateway version | Assessment for CVE-2026-90970 | Patched release |
|---|---|---|
| 18.1.6 or later, but earlier than 19.2.4 | Affected range | 19.2.4 |
| 19.3 earlier than 19.3.2 | Affected range | 19.3.2 |
| 19.4 earlier than 19.4.1 | Affected range | 19.4.1 |
If the gateway falls within one of these ranges, GitLab identifies it as affected and recommends upgrading to the corresponding patched branch release as soon as possible. These thresholds apply to the AI Gateway version, not the GitLab application version. If you cannot establish the gateway’s running version or image, treat that as an unresolved inventory question and verify it through the deployment method you use rather than assuming the gateway is patched.
Upgrade and verify a self-hosted gateway
- Identify each gateway deployment. Use your installation method’s configuration and runtime state to find the AI Gateway instances serving your environment.
- Determine what is running. Inspect the deployed gateway version or image, not only the desired configuration. Follow the relevant steps in GitLab’s installation and update documentation.
- Choose the matching patched release. Upgrade an affected 18.1.6-or-later, pre-19.2.4 gateway to 19.2.4; a pre-19.3.2 version in the 19.3 branch to 19.3.2; or a pre-19.4.1 version in the 19.4 branch to 19.4.1.
- Confirm the updated deployment. After applying the update, check the running deployment or image again to verify that the patched release is actually in use.
For Helm or Kubernetes deployments
Check the image pull policy and the image identity as part of the update. GitLab notes that IfNotPresent can leave a node using an already-cached image when an image tag has not changed. The installation documentation discusses using image digests to ensure that the intended patched image is pulled. Verify the running image after deployment rather than treating an updated manifest alone as proof of remediation.
Do not confuse this issue with CVE-2026-1868
CVE-2026-1868 was a separate, earlier AI Gateway template-expansion issue. Its fixes—18.6.2, 18.7.1, and 18.8.1—are not the patch guidance for CVE-2026-90970. Use the releases in the October 2026 advisory for the RCE addressed here. The earlier issue is documented in GitLab’s 18.6.2, 18.7.1, and 18.8.1 patch release and its CVE-2026-1868 record.
Quick Recap
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.
