CVE-2026-14934: Google Cloud Privilege Escalation Flaw

CVE-2026-14934 Overview

CVE-2026-14934 is a missing authorization vulnerability [CWE-862] affecting the repository creation functionality in Google Cloud BigQuery, Dataform, and Colab Enterprise. The flaw exists in versions deployed between October 2025 and May 10, 2026, on Google Cloud Platform (GCP). An authenticated attacker can exploit the missing authorization check to escalate privileges and perform cross-tenant repository takeover. Google patched the vulnerability on May 10, 2026, and no customer action is required. The issue is tracked in Google Cloud Support Bulletin GCP-2026-047.

Critical Impact
Authenticated attackers can bypass tenant isolation to hijack repositories across tenant boundaries in BigQuery, Dataform, and Colab Enterprise, compromising confidentiality, integrity, and availability of customer data.

Affected Products

Google Cloud BigQuery (October 2025 through May 10, 2026)
Google Cloud Dataform (October 2025 through May 10, 2026)
Google Cloud Colab Enterprise (October 2025 through May 10, 2026)

Discovery Timeline

May 10, 2026 - Google Cloud releases the fix on the platform
July 13, 2026 - CVE-2026-14934 published to NVD
July 13, 2026 - Last updated in NVD database

Technical Details for CVE-2026-14934

Vulnerability Analysis

The vulnerability originates in the repository creation workflow shared across BigQuery, Dataform, and Colab Enterprise. These services expose repository management APIs that allow authenticated GCP users to create and manage source-controlled assets such as notebooks, SQL workflows, and Dataform pipelines. The service failed to enforce tenant-scoped authorization when repositories were created, enabling an authenticated caller to reach repository objects belonging to other tenants.

Because the flaw resides in a shared multi-tenant control plane, the impact extends beyond a single project boundary. An attacker with valid GCP credentials can escalate privileges and gain control of resources outside their own organization. The CWE-862 classification confirms the root defect is the absence of an authorization check on a privileged operation.

Root Cause

The repository creation endpoint did not verify that the calling identity had authorization on the target tenant or project before performing state-changing operations. The service trusted request-level parameters without cross-checking them against the caller's Identity and Access Management (IAM) permissions, breaking tenant isolation.

Attack Vector

Exploitation requires network access to the GCP API surface and low-privilege authentication. No user interaction is required. An attacker abuses the repository creation API to reference repositories associated with a victim tenant, taking over those repositories and gaining read and write access to their contents. This can be leveraged to plant malicious code in notebooks or SQL workflows executed by the victim's service accounts.

No public proof-of-concept has been released, and the vulnerability was remediated server-side by Google before disclosure. See the Google Cloud Support Bulletin for the official advisory.

Detection Methods for CVE-2026-14934

Indicators of Compromise

Unexpected repository creation events in BigQuery, Dataform, or Colab Enterprise audit logs originating from identities outside the resource's owning project.
Cloud Audit Log entries showing google.cloud.dataform.v1beta1.Dataform.CreateRepository or equivalent Colab Enterprise API calls from unfamiliar principals.
Modifications to notebook or Dataform workflow contents that do not correspond to known developer activity.
Unusual cross-project or cross-organization API calls preceding repository state changes.

Detection Strategies

Review Cloud Audit Logs between October 2025 and May 10, 2026 for repository create, update, and IAM binding operations initiated by non-owner principals.
Correlate service account activity in Dataform and Colab Enterprise with expected CI/CD pipelines and flag deviations.
Baseline repository creation frequency per project and alert on statistical outliers.

Monitoring Recommendations

Ingest GCP Cloud Audit Logs into a centralized SIEM or data lake for retention beyond the default window and retroactive hunting.
Enable Data Access audit logs for BigQuery, Dataform, and Colab Enterprise to capture read operations against repository contents.
Monitor IAM policy changes on Dataform repositories and Colab Enterprise runtimes for unauthorized grants.

How to Mitigate CVE-2026-14934

Immediate Actions Required

No customer action is required. Google patched the vulnerability platform-side on May 10, 2026.
Conduct a retrospective audit of repository inventories and IAM bindings in BigQuery, Dataform, and Colab Enterprise for the exposure window.
Rotate any secrets, service account keys, or tokens stored in Dataform repositories or Colab notebooks that may have been exposed.
Review executed notebook and workflow code for unauthorized modifications introduced before May 10, 2026.

Patch Information

Google Cloud deployed the fix on May 10, 2026 across all affected services. Because BigQuery, Dataform, and Colab Enterprise are managed services, the remediation was applied server-side without requiring customer intervention. Refer to Google Cloud Support Bulletin GCP-2026-047 for advisory details.

Workarounds

No workarounds are required post-patch. Prior to the fix, no customer-side mitigation was available since the flaw resided in Google-managed infrastructure.
Apply least-privilege IAM roles for Dataform and Colab Enterprise as a defense-in-depth measure.
Enforce VPC Service Controls around BigQuery and related analytics services to restrict cross-tenant API reachability.

bash

# Example: enumerate Dataform repositories per project for audit review
gcloud dataform repositories list \
  --project=YOUR_PROJECT_ID \
  --region=YOUR_REGION \
  --format="table(name,createTime,updateTime)"

# Example: export Cloud Audit Logs for retrospective analysis of the exposure window
gcloud logging read \
  'resource.type="dataform.googleapis.com/Repository" AND \
   protoPayload.methodName:"CreateRepository" AND \
   timestamp>="2025-10-01T00:00:00Z" AND timestamp<="2026-05-10T23:59:59Z"' \
  --project=YOUR_PROJECT_ID \
  --format=json > dataform_repo_audit.json