External risk intelligence

Google Cloud Path Traversal Vulnerability Allows Reading and Writing Files Across Repositories

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-126054

The vulnerability affects specific managed Google Cloud Platform services (Dataform, BigQuery Studio, Colab Enterprise) which are accessed via the Google Cloud console or authenticated API endpoints. These services are typically used within controlled, authenticated cloud environments rather than being exposed directly to the public internet as standalone web-facing services.

Path Traversal

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability in Google Cloud platform services allows authenticated users to read private files and create arbitrary files across repositories by exploiting how workspace directories and Git integrations are handled. While a patch was deployed on October 10, 2026, confirming relevance is the primary concern.

  • Unauthenticated access to files and arbitrary file creation.
  • Critical risk for authenticated users in affected services.
  • Confirm relevance and exposure in your cloud environment.

Attack Path

How an attacker could exploit the issue

An attacker with valid credentials could exploit this vulnerability by manipulating workspace operations and Git integration requests. This could allow them to navigate beyond intended directory boundaries, potentially leading to the reading of sensitive files or the creation of arbitrary files within or across repositories.

  • Authenticated remote access required.
  • Crafted workspace operations trigger it.
  • Read private files, create arbitrary files.

Live Threat

Current exploitation, exposure, and threat context

An authenticated attacker could read or create arbitrary files within tenant repositories in Google Cloud Dataform, BigQuery Studio, and Colab Enterprise. This could occur when specific workspace operations or Git integration requests are crafted to exploit the vulnerability.

  • Tenant repository files at risk.
  • Crafted workspace or Git requests.
  • Unauthorized file access or modification.

Operational Fix

Recommended remediation, mitigation, and detection steps

Google Cloud Platform security and platform teams are likely responsible for addressing this vulnerability within their managed services. The first practical step is to confirm the patching status of affected services and ensure no residual risk exists.

  • Own the remediation of Google Cloud managed services.
  • Verify that Google Cloud services are patched.
  • Confirm no residual tenant repository risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Google Cloud Dataform, BigQuery Studio, and Colab Enterprise?

These are managed services on the Google Cloud Platform designed for data engineering and analysis. Dataform helps teams manage SQL workflows, BigQuery Studio provides an integrated environment for data science and analytics, and Colab Enterprise offers a collaborative notebook environment. They all rely on workspace directories and Git integrations to help users version control and organize their data projects.

How does the path traversal vulnerability in CVE-2026-126054 work?

This flaw involves Improper Limitation of a Pathname to a Restricted Directory, also known as Path Traversal (CWE-22). It occurs when software fails to properly validate file paths during directory operations. By sending specially crafted requests, an attacker can trick the system into accessing or creating files outside of the intended, authorized folder boundaries, essentially breaking the logical silos between different workspaces or repositories.

What triggers the CVE-2026-126054 vulnerability?

The issue is triggered when a user with valid credentials sends specifically crafted workspace operations or Git integration requests to the service. Simple, legitimate use of these tools does not trigger the bug. An attacker must intentionally manipulate these service requests to bypass directory restrictions; the vulnerability cannot be triggered by routine navigation or standard data analysis tasks.

Is my cloud environment at risk from this vulnerability?

According to Halo Surface Signal, this vulnerability is considered unlikely to affect public-facing assets because these services are managed Google Cloud components accessed through the cloud console or authenticated APIs. The risk is primarily internal, requiring an attacker to already have valid authentication to the platform. Organizations should assess if they utilize these specific services and rely on cloud-level identity controls.

What should I do to address CVE-2026-126054?

No customer action is required. Google patched this vulnerability in their managed services on October 10, 2026. Because these are cloud-native services, the provider handles the underlying infrastructure security. You can confirm your environment's status by reviewing your service logs or the official Google Cloud release notes for these products to ensure you are aware of the update timeline.

References