Google Cloud Vertex AI Workbench prior 01/30/2026 information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Cloud Vertex AI Workbench. It has been classified as problematic. This issue affects some unknown processing. This manipulation causes information disclosure. The identification of this vulnerability is CVE-2026-2244. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is recommended.
Details
A vulnerability has been found in Google Cloud Vertex AI Workbench and classified as problematic. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:
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 advisory is shared at docs.cloud.google.com. This vulnerability is known as CVE-2026-2244 since 02/09/2026. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/26/2026). MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 01, 30 or 2026 eliminates this vulnerability.
The vulnerability is also documented in the databases at EUVD (EUVD-2026-8853) and CERT Bund (WID-SEC-2026-0541). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Google Cloud Platform
Product
Type
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Vertex AI Workbench 01/30/2026
Timeline
01/30/2026 Countermeasure disclosed02/09/2026 CVE reserved
02/26/2026 Advisory disclosed
02/26/2026 VulDB entry created
02/26/2026 VulDB entry last update
Sources
Advisory: docs.cloud.google.comStatus: Confirmed
CVE: CVE-2026-2244 (🔒)
GCVE (CVE): GCVE-0-2026-2244
GCVE (VulDB): GCVE-100-347989
EUVD: 🔒
CERT Bund: WID-SEC-2026-0541 - Google Cloud Platform (Vertex AI Workbench): Schwachstelle ermöglicht Erlangen von Benutzerrechten
Entry
Created: 02/26/2026 16:11Updated: 02/26/2026 18:01
Changes: 02/26/2026 16:11 (68), 02/26/2026 16:35 (7), 02/26/2026 18:01 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.