dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-1727

CRITICAL · 9.1 CVSS v4.0 Published 2026-02-06
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 No privileges Zero-click

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
The Agentspace service was affected by a vulnerability that exposed sensitive information due to the use of predictable Google Cloud Storage bucket names. These names were utilized for error logs and temporary staging during data imports from GCS and Cloud SQL. This predictability allowed an attacker to engage in "bucket squatting" by establishing these buckets before a victim's initial use. All versions after December 12th, 2025 have been updated to protect from this vulnerability. No user action is required for this.

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

The Agentspace service used predictable Google Cloud Storage bucket names for error logs and temporary staging during data imports from GCS and Cloud SQL. Attackers could engage in 'bucket squatting' by pre-creating these predictably-named buckets before victim initial use, allowing them to intercept sensitive data.

MitigationNo user action required. The vendor has patched this vulnerability in all versions released after December 12th, 2025.

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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:L/SI:L/SA:L/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. Identify if Agentspace service is deployed
    Check your Google Cloud environment for Agentspace resources. Use 'gcloud agentspace list' or review your Cloud Console for Agentspace instances. Check infrastructure-as-code templates (Terraform, Deployment Manager) for 'agentspace' resource definitions.
    Affected if Agentspace service is not deployed in your environment
  2. Determine the installed Agentspace version
    Run 'gcloud agentspace describe [INSTANCE_ID]' or check the Cloud Console Agentspace details page for the version number. Compare against the patched version released after December 12th, 2025.
    Affected if The version is older than the December 2025 patch or cannot be verified
  3. Verify if data import from GCS or Cloud SQL is enabled
    Review Agentspace configuration for data import features. Check for 'import', 'gcs', or 'cloudsql' related settings using 'gcloud agentspace get-config' or examine the Agentspace service account permissions for storage and Cloud SQL access.
    Affected if Data import from GCS or Cloud SQL has been configured or used
  4. Inspect Cloud Storage bucket names used by Agentspace
    Review Cloud Audit Logs for Agentspace service operations. Look for 'storage.buckets.create' events or check your existing GCS buckets for names containing patterns like 'agentspace', 'staging', 'temp', 'import', or 'error' in the bucket naming convention.
    Affected if Buckets follow a predictable naming pattern (e.g., containing 'agentspace-staging-*' or similar sequential/predictable names)
  5. Check audit logs for historical data import operations
    Search Cloud Audit Logs for 'agentspace' and 'import' operations. Filter for 'storage.objects.create' or 'cloudsql.instances.export' events initiated by the Agentspace service account.
    Affected if Data import operations have occurred using Agentspace before the December 2025 patch date

A user is affected if they have deployed Agentspace with data import from GCS or Cloud SQL enabled, and their version predates the December 2025 patch.

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 user action required. The vendor has patched this vulnerability in all versions released after December 12th, 2025.

Recommended fix High confidence
  1. No user action required. This vulnerability was patched server-side by Google.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.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-1727 — 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-1727 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