PULSE the living trend engine
🤖 Open Intelligence Dossier available for AI agents & citation View Markdown (.md) →
◼ Archived Business

GitLab warns of critical RCE vulnerability in AI Gateway service

GitLab has patched a critical 9.9 rated remote code execution vulnerability in its AI Gateway service that was being actively exploited.

5sources
5articles
3velocity
+0%since first seen
42d agofirst detected

Velocity

How fast coverage is spreading — measured hourly from article rate × source diversity. How this works →

📍 How it ended

GitLab warned of a critical remote code execution vulnerability in its AI Gateway service that was under active exploitation and enabled unauthenticated data exfiltration and command execution on self-hosted servers. In response to the issue, GitLab issued patches to resolve the 9.9 severity flaw.

Epilogue added 30d ago, after coverage quieted.

The brief

GitLab has issued a warning and released patches for a critical vulnerability identified as CVE-2026-90970. This flaw exists within the company's AI Gateway service and is categorized as a remote code execution (RCE) vulnerability. According to coverage, the security flaw allows for command execution on servers that are self-hosted. The vulnerability is particularly severe because it allows unauthenticated users to perform data exfiltration, meaning attackers do not need valid credentials to access or remove sensitive information from the affected systems. Multiple cybersecurity and tech news outlets have emphasized the severity of this event. BleepingComputer reports on the warning issued by GitLab regarding the AI Gateway service, while The Hacker News highlights that the flaw enables command execution specifically on self-hosted servers.

InfoQ reports that the vulnerability was under active exploitation at the time of reporting, focusing on the risk of unauthenticated data exfiltration. Additionally, reports from forkast.news and Pasquale Pillitteri confirm that GitLab has officially released patches to address the security gap. The technical stakes of this vulnerability are reflected in its score, which is listed as a 9.9. This high rating indicates a critical level of risk to the infrastructure of organizations utilizing the AI Gateway. The context provided by the coverage suggests that the primary target of this vulnerability is the self-hosted environment, where administrators are responsible for their own server maintenance and patching schedules. The ability for an unauthenticated actor to execute commands and exfiltrate data makes this a high-priority security event for GitLab users.

Moving forward, the focus remains on the deployment of the available patches. Because coverage from InfoQ indicates the flaw was under active exploitation, the immediate priority for affected organizations is to apply the updates released by GitLab. The situation highlights the ongoing risks associated with AI-integrated services and the necessity of rapid patching cycles for self-hosted enterprise software. Further updates will likely depend on the rate of adoption of these patches across self-hosted GitLab installations.

Synthesized by PULSE from the headlines below under a strict no-invention contract. ✓ fact-checked: all claims supported by sources Updated 40d ago.

Quick answers

What is the CVE identifier for this vulnerability?

The vulnerability is identified as CVE-2026-90970.

Who is most at risk from this flaw?

The flaw allows for command execution specifically on self-hosted servers.

What is the severity score of the vulnerability?

The vulnerability has been assigned a critical score of 9.9.

Coverage (5)

Topics

Related trends

\n \n \n \n \n \n \n