Security readout for executives and security teams
Plain-English summary
CVE-2026-2244 affected Google Cloud Vertex AI Workbench during a defined window. An attacker with some privileges could abuse a built-in startup script to steal valid Google Cloud access tokens belonging to other users. Google states instances after January 30, 2026 are patched and no user action is required.
Executive priority
Treat as high priority for cloud teams that used Vertex AI Workbench during the affected window. The main business risk is unauthorized access using valid Google Cloud tokens. Google reports the service is patched after January 30, 2026, so focus on exposure review and evidence of misuse.
Technical view
The issue is a CWE-200 sensitive data exposure in Vertex AI Workbench, CVSS 8.4 high. The CVE describes network-accessible exploitation with low attack complexity, low privileges, and user interaction required. Impact centers on confidentiality and downstream access through exposed Google Cloud tokens. The affected period is July 21, 2025 through January 30, 2026.
Likely exposure
Organizations using Google Cloud Vertex AI Workbench between July 21, 2025 and January 30, 2026 should assess exposure. Sources do not identify specific instance configurations beyond Vertex AI Workbench and the affected date window. Instances after January 30, 2026 are described as patched.
Exploitation context
The source bundle does not report active exploitation, and the CVE is not marked as CISA KEV. The described attack requires an attacker with low privileges and user interaction, then abuses a built-in startup script to exfiltrate other users’ valid Google Cloud access tokens.
Researcher notes
Public details are limited. The CVE identifies token exfiltration through abuse of a built-in startup script but does not provide detailed affected versions, exploit indicators, or detection logic. Avoid assuming active exploitation. Validation should focus on asset timing, vendor release notes, and cloud audit evidence.
Mitigation direction
- Confirm Vertex AI Workbench instances are covered by Google’s post-January 30, 2026 patched state.
- Review Google Vertex AI Workbench release notes and vendor guidance for any environment-specific actions.
- If token exposure is suspected, follow Google Cloud credential revocation and incident response guidance.
Validation and detection
- Inventory Vertex AI Workbench instances active between July 21, 2025 and January 30, 2026.
- Confirm instance creation or update dates against Google’s patched-after-January-30 statement.
- Review Google Cloud audit logs for unusual access token use during the exposure window.
- Check internal incident records for suspicious startup script or Workbench activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-2244 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.4 (4.0)
- Known Exploited
- No
- Published
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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
8.4HighVector: 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
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.