● High · CVSS 8.4

How to Fix CVE-2026-2244: Information exposure in Vertex AI Workbench

Q: What is the CVSS score for CVE-2026-2244?

8.4 (High). Vector: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H/U:Clear`.

Q: Where is the official advisory for CVE-2026-2244?

The vendor advisory is at [https://docs.cloud.google.com/vertex-ai/docs/workbench/release-notes#February_20_2026](https://docs.cloud.google.com/vertex-ai/docs/workbench/release-notes#February_20_2026). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-2244.

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-2244 is a information exposure in Google Cloud Vertex AI Workbench. The fix is to apply the vendor patch noted below.

⚡ At a glance


Severity	8.4 (High)
Actively exploited?	No public listing in CISA KEV
Affected	Vertex AI Workbench 7/21/2025 to <01/30/2026
Fixed in	See vendor advisory
Type (CWE)	CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

What is CVE-2026-2244?

A vulnerability in Google Cloud Vertex AI Workbench from 7/21/2025 to 01/30/2026 allows an attacker to exfiltrate valid Google Cloud access tokens of other users via abuse of a built-in startup script.

All instances after January 30th, 2026 have been patched to protect from this vulnerability. No user action is required for this. The CVSS base score is 8.4 (High), which puts this in the upper risk band and warrants a fast patch cycle. The official advisory is at https://docs.cloud.google.com/vertex-ai/docs/workbench/release-notes#February_20_2026.

Am I affected?

Check the version of Vertex AI Workbench you are running and compare it against the Affected row above (Vertex AI Workbench 7/21/2025 to <01/30/2026). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s vertex-ai-workbench 2>/dev/null | grep -i ^Version
rpm -q vertex-ai-workbench 2>/dev/null
command -v vertex-ai-workbench >/dev/null && vertex-ai-workbench --version 2>/dev/null


# Windows (PowerShell)
Get-Package -Name "*Vertex AI Workbench*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "Vertex AI Workbench" 2>$null

How to fix CVE-2026-2244

Upgrade Vertex AI Workbench to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade vertex-ai-workbench
dpkg -s vertex-ai-workbench | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh vertex-ai-workbench -y
# or for older releases:
sudo yum update vertex-ai-workbench -y
rpm -q vertex-ai-workbench

SUSE / openSUSE


sudo zypper refresh
sudo zypper update vertex-ai-workbench
rpm -q vertex-ai-workbench

Node.js / npm


# Update the affected package in your project
npm install Vertex AI Workbench@latest
npm ls Vertex AI Workbench
npm audit fix

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-2244 affecting Vertex AI Workbench
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-2244-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*Vertex AI Workbench*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\vertex-ai-workbench-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\Vertex AI Workbench" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "Vertex AI Workbench" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "Vertex AI Workbench"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)


#!/usr/bin/env bash
# Fix script for CVE-2026-2244 affecting Vertex AI Workbench
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-2244-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s vertex-ai-workbench 2>/dev/null | grep -i ^Version || echo "vertex-ai-workbench not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q vertex-ai-workbench || echo "vertex-ai-workbench not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-2244-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/vertex-ai-workbench /etc/vertex-ai-workbench.d /etc/vertex-ai-workbench.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y vertex-ai-workbench
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y vertex-ai-workbench
elif command -v yum >/dev/null; then
    yum update -y vertex-ai-workbench
elif command -v zypper >/dev/null; then
    zypper --non-interactive update vertex-ai-workbench
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s vertex-ai-workbench 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q vertex-ai-workbench
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)


# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)


New-NetFirewallRule -DisplayName "Block-CVE-2026-2244" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-2244"

Disable the affected service (Linux)


sudo systemctl stop vertex-ai-workbench 2>/dev/null || true
sudo systemctl disable vertex-ai-workbench 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.


# Linux
dpkg -s vertex-ai-workbench 2>/dev/null | grep -i ^Version
rpm -q vertex-ai-workbench 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true


# Windows
Get-Package -Name "*Vertex AI Workbench*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-9116: Critical Vulnerability in Chrome — Critical Vulnerability in Chrome
How to Fix CVE-2026-1393: Critical Vulnerability in Add Google Social Profiles to Knowledge Graph Box — Critical Vulnerability in Add Google Social Profiles to Knowledge Graph Box
How to Fix CVE-2026-5912: Chrome (Bundle Sibling) , Chrome (Bundle Sibling)
How to Fix CVE-2026-5284: Chrome (Bundle Sibling) , Chrome (Bundle Sibling)
How to Fix CVE-2026-8553: Use-After-Free in Chrome , Use-After-Free in Chrome

Is CVE-2026-2244 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-2244?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

What is the CVSS score for CVE-2026-2244?

8.4 (High). Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H/U:Clear.

Where is the official advisory for CVE-2026-2244?

The vendor advisory is at https://docs.cloud.google.com/vertex-ai/docs/workbench/release-notes#February_20_2026. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-2244.

References

Official vendor advisory: https://docs.cloud.google.com/vertex-ai/docs/workbench/release-notes#February_20_2026
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2244
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*