Skip to main content
Menu
CVEs

Google Cloud Dataform cross-tenant file read and write in workspace operations

CVE-2026-126054Published , updated

9.3CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 2026-10-10
Who is exposed
Specific setups only

Summary

A path traversal flaw in Google Cloud Dataform, BigQuery Studio, and Colab Enterprise lets a remote attacker with a low-privilege login read private files and create arbitrary files across tenant repositories. The attacker reaches it through crafted workspace operations and Git integration requests.

Written by a model

Original description

A Path Traversal vulnerability in workspace directory handling and Git integration in Google Cloud Dataform, BigQuery Studio and Colab Enterprise on Google Cloud Platform allows an authenticated remote attacker to read private files and create arbitrary files across tenant repositories using crafted workspace operations and Git integration requests.

This vulnerability was patched on 10 October 2026, and no customer action is needed.

Who should check

Teams using Dataform, BigQuery Studio or Colab Enterprise on Google Cloud, including workspace directory and Git integration features.

“A path traversal vulnerability in workspace directory handling and Git integration was discovered in Dataform, BigQuery Studio, and Colab Enterprise.”

docs.cloud.google.com

What to do

Upgrade to a fixed version: 2026-10-10.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-126054 (Path Traversal in Dataform, BigQuery Studio and Colab Enterprise allows Cross-Tenant File Read and Write), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126054 (entry last updated 2026-11-20):
Affected:
- Google Cloud Dataform: fixed in 2026-10-10
- Google Cloud BigQuery Studio: fixed in 2026-10-10
- Google Cloud Colab Enterprise: fixed in 2026-10-10
Fixed versions: 2026-10-10.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-126054 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126054 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://docs.cloud.google.com/support/bulletins/#gcp-2026-084
- https://docs.cloud.google.com/bigquery/docs/release-notes#November_19_2026
- https://docs.cloud.google.com/dataform/docs/release-notes#November_19_2026
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126054
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126054"}.

Affected versions

cve.now Index

17Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.3/10CVSS 9.3
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 24 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Evidence 5

Questions about CVE-2026-126054

Is CVE-2026-126054 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-126054?

Dataform: before 2026-10-10. BigQuery Studio: before 2026-10-10. Colab Enterprise: before 2026-10-10.

Source: cve.now feed data

How do I fix CVE-2026-126054?

Upgrade to a fixed version: 2026-10-10.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.