For CVE-2026-90970, upgrade an affected customer-operated Self-Hosted AI Gateway to the fixed version for its release line: 19.2.4, 19.3.2, or 19.4.1. First establish whether your deployment uses GitLab-hosted or Self-Hosted AI Gateway: GitLab says its hosted gateways are already patched, so customers using those gateways do not need to take action for this advisory. A separate gateway deployment is not necessarily updated by upgrading the GitLab instance.
Is this an AI Gateway update or a GitLab instance upgrade?
This advisory concerns the GitLab AI Gateway, a component that may be operated separately from the GitLab instance. The first decision is who runs the gateway, because that determines whether you need to act and which update procedure applies.
As an Amazon Associate I earn from qualifying purchases.
| Gateway deployment | Who operates it | Action for CVE-2026-90970 | Update procedure |
|---|---|---|---|
| GitLab-hosted AI Gateway | GitLab | No customer update is required for this advisory; GitLab says hosted gateways are patched. | No customer-operated gateway image to update for this issue. |
| Self-Hosted AI Gateway | Your organization | Check the deployed release and update if it is in an affected range. | Follow GitLab’s Self-Hosted AI Gateway installation and update documentation for your deployment method. |
GitLab.com, GitLab Dedicated, and Self-Managed instances using a GitLab-hosted gateway need no action for this advisory. If you operate a separate Self-Hosted AI Gateway, upgrading GitLab core alone should not be treated as proof that the gateway has been updated.
What does CVE-2026-90970 affect?
GitLab describes a critical issue in which, under certain conditions, an authenticated user with Duo Agent Platform access could escape the prompt-template sandbox using a specially crafted flow configuration. The result could be arbitrary command execution on the AI Gateway. GitLab rates the advisory CVSS 9.9.
#1 Best Overall
- POWERFUL SECURITY KEY: The Security Key C NFC is the essential physical passkey for protecting your digital life from phishing attacks. It ensures only you can access your accounts.
- WORKS WITH 1000+ ACCOUNTS: Compatible with Google, Microsoft, and Apple. A single Security Key C NFC secures 100 of your favorite accounts, including email, password managers, and more.
- FAST & CONVENIENT LOGIN: Plug in your Security Key C NFC via USB-C and tap it, or tap it against your phone (NFC) to authenticate. No batteries, no internet connection, and no extra fees required.
- TRUSTED PASSKEY TECHNOLOGY: Uses the latest passkey standards (FIDO2/WebAuthn & FIDO U2F) but does not support One-Time Passwords. For complex needs, check out the YubiKey 5 Series.
- BUILT TO LAST: Made from tough, waterproof, and crush-resistant materials. Manufactured in Sweden and programmed in the USA with the highest security standards.
Which AI Gateway versions are affected, and what fixes the vulnerability?
GitLab’s advisory lists these affected ranges and fixed releases:
| AI Gateway release line | Affected versions | Fixed version listed by GitLab |
|---|---|---|
| 18.1.6 through the 19.2 line | Versions from 18.1.6 up to, but not including, 19.2.4 | 19.2.4 |
| 19.3 | Versions before 19.3.2 | 19.3.2 |
| 19.4 | Versions before 19.4.1 | 19.4.1 |
Choose the fixed release appropriate to your existing release line and compatibility requirements. These are AI Gateway versions: do not substitute a GitLab core version number for a gateway image version without checking the gateway documentation and the tags available for your deployment.
Rank #2
- POWERFUL SECURITY KEY: The YubiKey 5C NFC is the most versatile physical passkey, protecting your digital life from phishing attacks. It ensures only you can access your accounts
- WORKS WITH 1000+ ACCOUNTS: Compatible with popular accounts like Google, Microsoft, and Apple. A single YubiKey 5C NFC secures 100+ of your favorite accounts, including email, password managers, and more
- FAST & CONVENIENT LOGIN: Plug in your YubiKey 5C NFC via USB and tap it, or tap it against your phone (NFC), to authenticate. No batteries, no internet connection, and no extra fees required
- MOST SECURE PASSKEY: Supports FIDO2/WebAuthn, FIDO U2F, Yubico OTP, OATH-TOTP/HOTP, Smart card (PIV), and OpenPGP. That means it’s versatile, working almost anywhere you need it
- PRIMARY & SPARE KEYS: Just like having a spare house key, we recommend buying two YubiKeys - one for daily use and one as a spare. That way you’ll never get locked out of your accounts
How do I upgrade GitLab AI Gateway safely?
Use GitLab’s live Self-Hosted AI Gateway installation and update documentation for the commands and sequence that match your deployment method. GitLab’s general upgrade documentation also links to pre-upgrade preparation, method-specific procedures, troubleshooting, rollback, and release maintenance information. The steps below are a planning and verification workflow, not a universal command sequence.
- Confirm the gateway deployment. Establish whether you use GitLab-hosted AI Gateway or operate a Self-Hosted AI Gateway yourself. Only the latter requires you to deploy the fix for this advisory.
- Record the running gateway image tag and release line. Inspect the deployment using the method your organization uses, and note the current image tag before making changes. The GitLab installation guide recommends stable releases with explicit version tags; it warns that nightly builds do not guarantee backward compatibility.
- Select the appropriate fixed gateway release. Match your current release line to 19.2.4, 19.3.2, or 19.4.1 as listed in GitLab’s advisory. The install guide’s general rule is to use the latest matching
self-hosted-vX.Y.*-eeimage for the GitLab version line. Its example for GitLabv18.2.1-eeselectsself-hosted-v18.2.2-eewhen that is the latest listed matching image. Because the security advisory’s fixed gateway versions must also be matched to the available tags and your deployment, confirm that mapping in the current documentation before proceeding. - Prepare the change and rollback plan. Follow the pre-upgrade checks and the procedure for your installation method. Record the current image and relevant configuration so your team can use the deployment-specific rollback guidance if validation fails. The sources do not establish one universal restart sequence or downtime duration.
- Preserve required signing configuration. Self-hosted deployments require RSA 2048-bit PEM JWT signing and validation key pairs for relevant services. Keep the keys secure and available to the services that need them; missing keys can cause token creation errors.
- Apply the update using the documented method. Use the current GitLab procedure for your deployment rather than a generic Docker or Helm command. The correct sequence depends on how the gateway is installed and operated.
- Verify the deployed image and service behavior. Confirm that the running gateway uses the intended fixed image tag, then exercise the Duo and other gateway features used in your environment and check service logs and monitoring for errors.
What should I check before restoring or tightening network access?
GitLab recommends restricting outbound network access from a self-hosted gateway to the destinations it needs, including GitLab, model providers, and—unless you use an offline license—customers.gitlab.com. Validate firewall changes outside production first: rules that are too restrictive can disrupt gateway functionality. Treat this as a deployment-specific security control, not a substitute for installing the fixed version.
Rank #3
- POWERFUL SECURITY KEY: The YubiKey 5 NFC is the most versatile physical passkey, protecting your digital life from phishing attacks. It ensures only you can access your accounts
- WORKS WITH 1000+ ACCOUNTS: Compatible with popular accounts like Google, Microsoft, and Apple. A single YubiKey 5 NFC secures 100+ of your favorite accounts, including email, password managers, and more
- FAST & CONVENIENT LOGIN: Plug in your YubiKey 5 NFC via USB and tap it, or tap it against your phone (NFC), to authenticate. No batteries, no internet connection, and no extra fees required
- MOST SECURE PASSKEY: Supports FIDO2/WebAuthn, FIDO U2F, Yubico OTP, OATH-TOTP/HOTP, Smart card (PIV), and OpenPGP. That means it’s versatile, working almost anywhere you need it
- PRIMARY & SPARE KEYS: Just like having a spare house key, we recommend buying two YubiKeys - one for daily use and one as a spare. That way you’ll never get locked out of your accounts
How can I avoid confusing this with an older AI Gateway advisory?
GitLab published a separate critical AI Gateway advisory on February 6, 2026, for CVE-2026-1868, an insecure template expansion issue. That advisory lists fixes in 18.6.2, 18.7.1, and 18.8.1. Those versions address the earlier CVE, not CVE-2026-90970. If you are working from an older ticket or article, match its CVE identifier and publication date to the current advisory before applying version guidance.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How does GitLab handle security releases?
GitLab’s security FAQ says it publishes scheduled monthly security releases and ad-hoc releases for critical vulnerabilities, with fixes backported to the current release and the two previous major.minor versions. GitLab recommends using at least the latest security release for a supported version. For this gateway issue, use the specific affected ranges and fixed gateway versions in the CVE-2026-90970 advisory rather than inferring gateway remediation from the general GitLab core release policy.
Quick Recap
Best Value
- POWERFUL SECURITY KEY: The YubiKey 5 is a versatile physical passkey that protects your digital life from phishing attacks. It ensures only you can access your accounts.
- WORKS WITH 1000+ ACCOUNTS: Compatible with popular accounts like Google, Microsoft, and Apple. A single YubiKey 5 secures 100+ of your favorite accounts, including email, password managers, and more.
- FAST & CONVENIENT LOGIN: Plug in your YubiKey 5 via USB and tap it to authenticate. No batteries, no internet connection, and no extra fees required.
- MOST SECURE PASSKEY: Supports FIDO2/WebAuthn, FIDO U2F, Yubico OTP, OATH-TOTP/HOTP, Smart card (PIV), and OpenPGP. That means it’s versatile, working almost anywhere you need it.
- BUILT TO LAST: Made from tough, waterproof, and crush-resistant materials. Manufactured in Sweden and programmed in the USA with the highest security standards.
Rank #4
- POWERFUL SECURITY KEY: The Security Key NFC is the essential physical passkey for protecting your digital life from phishing attacks. It ensures only you can access your accounts.
- WORKS WITH 1000+ ACCOUNTS: Compatible with Google, Microsoft, and Apple. A single Security Key NFC secures 100 of your favorite accounts, including email, password managers, and more.
- FAST & CONVENIENT LOGIN: Plug in your Security Key NFC via USB-A and tap it, or tap it against your phone (NFC) to authenticate. No batteries, no internet connection, and no extra fees required.
- TRUSTED PASSKEY TECHNOLOGY: Uses the latest passkey standards (FIDO2/WebAuthn & FIDO U2F) but does not support One-Time Passwords. For complex needs, check out the YubiKey 5 Series.
- BUILT TO LAST: Made from tough, waterproof, and crush-resistant materials. Manufactured in Sweden and programmed in the USA with the highest security standards.
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.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →
