Skip to content
major vulnerability· requires attention

Token exfiltration via startup script could expose Google Cloud access tokens across users; automated patch mitigates risk.

Cloud

CVE-2026-2244

8.4
High
EPSS 0.25%Patch availableFeb 27, 2026

Token exfiltration via Vertex AI Workbench startup script; tokens of other users exposed.

common questions

Is CVE-2026-2244 being exploited?

Not confirmed. CVE-2026-2244 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. EPSS currently estimates a 0.25% probability of exploitation in the next 30 days.

How severe is CVE-2026-2244?

CVE-2026-2244 is rated High with a CVSS score of 8.4. 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-2244?

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

What does CVE-2026-2244 affect?

CVE-2026-2244 affects Google Cloud Vertex AI Workbench. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-2244?

No action needed; enable auto-patching and monitor token usage.

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

executive summary
technical analysis
affected
Google Cloud Vertex AI Workbench
impact

Exposes valid Google Cloud access tokens; attacker can impersonate users and access cloud resources.

action required

Monitor only

affected versions
Google Cloud Vertex AI Workbench
  • affected>= 7/21/2025 and < 01/30/2026

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