dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-14934

CRITICAL · 9.4 CVSS v4.0 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A Missing Authorization vulnerability in the repository creation functionality in Google Cloud BigQuery, Dataform and Colab Enterprise, in the versions between October 2025 and May 10th, 2026, on Google Cloud Platform, allows an authenticated attacker to escalate privileges and perform cross-tenant repository takeover. This vulnerability was patched on 10 May 2026, and no customer action is needed.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Missing authorization check in repository creation across BigQuery, Dataform, and Colab Enterprise allowed authenticated users to create or modify repositories outside their proper tenant boundary, enabling privilege escalation and cross-tenant repository takeover.

MitigationNo customer action required; Google patched the vulnerability server-side on May 10, 2026. Organizations should verify they are running post-May-2026 API versions and review audit logs for any suspicious repository creation events between October 2025 and May 2026.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:Clear

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify the BigQuery API version in use
    Query the BigQuery API metadata endpoint or check the client library version being used in your environment: gcloud bigquery --version or check the client library version in your application's dependency lock file
    Affected if The API version or client library predates the May 2026 patch date (any version before the server-side fix was applied)
  2. Verify the Dataform API version in use
    Query the Dataform API metadata or check the client library version: gcloud dataform --version or review application dependencies for @google-cloud/dataform version
    Affected if The API version or client library predates the May 2026 patch date
  3. Verify the Colab Enterprise API version in use
    Query the Colab Enterprise API metadata or check the client library version being used by any connected notebooks or workflows
    Affected if The API version or client library predates the May 2026 patch date
  4. Review Cloud Audit Logs for suspicious repository creation
    In Google Cloud Console, navigate to Cloud Audit Logs and filter for log entries with method 'CreateRepository' or 'UpdateRepository' in BigQuery, Dataform, or Colab Enterprise services between October 2025 and May 2026. Look for repository creations where the principal differs from the expected tenant owner
    Affected if Any repository creation or modification events exist where the authenticated user created a repository outside their expected tenant boundary (cross-tenant repository creation)
  5. Check for unexpected cross-tenant repository access patterns
    Review repository access logs and IAM permission audits to identify any repositories accessed by users from different tenants than the repository owner, particularly around the October 2025 to May 2026 window
    Affected if Any evidence of repositories being accessed or modified by principals outside their proper tenant boundary

You are affected if your environment used BigQuery, Dataform, or Colab Enterprise API versions prior to the May 2026 server-side patch AND suspicious cross-tenant repository creation events appear in audit logs between October 2025 and May 2026

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

No customer action required; Google patched the vulnerability server-side on May 10, 2026. Organizations should verify they are running post-May-2026 API versions and review audit logs for any suspicious repository creation events between October 2025 and May 2026.

Recommended fix High confidence

Post-May 10, 2026 versions of Google Cloud BigQuery, Dataform, and Colab Enterprise (no upgrade needed - patch applied by Google)

  1. No customer action required. Google has automatically patched this vulnerability on May 10, 2026.
  2. The fix was applied server-side by Google to all affected BigQuery, Dataform, and Colab Enterprise deployments.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Review / QA1.0 h
2.0 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14934 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-14934 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data