Skip to content
major vulnerability· requires attention

Affects GitLab (widely used enterprise SCM); RCE in AI Gateway could impact many organizations and warrants broad IT notification.

Applications

CVE-2026-90970

9.9
Critical
EPSS n/aPatch availableOct 3, 2026

Authenticated sandbox escape in GitLab AI Gateway enabling remote command execution.

common questions

Is CVE-2026-90970 being exploited?

Not confirmed. CVE-2026-90970 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-90970?

CVE-2026-90970 is rated Critical with a CVSS score of 9.9. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-90970?

Yes. A fix has been recorded for CVE-2026-90970. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-90970 affect?

CVE-2026-90970 affects GitLab AI Gateway >=18.1.6 and <19.2.4, GitLab AI Gateway 19.3.0 - 19.3.1, GitLab AI Gateway 19.4.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-90970?

Upgrade AI Gateway to 19.2.4+, 19.3.2+, or 19.4.1+; restrict Duo Agent access and audit logs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
GitLab AI Gateway >=18.1.6 and <19.2.4GitLab AI Gateway 19.3.0 - 19.3.1GitLab AI Gateway 19.4.0
impact

Authenticated user with Duo Agent access can escape prompt template sandbox to execute arbitrary commands on the AI Gateway (RCE, lateral movement).

action required

Immediate action required

affected versions
GitLab GitLab AI Gateway
  • affected>= 18.1.6 and < 19.2.4
  • affected>= 19.3 and < 19.3.2
  • affected>= 19.4 and < 19.4.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free