# CVE-2026-1727: Information Disclosure via Bucket Squatting in Google Cloud Agentspace.

> Attackers could read sensitive data by squatting on predictable storage buckets used for logs and staging in Google Cloud Agentspace.

- **Severity:** Critical 9.1 (`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/U:Clear`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Feb 2026
- **Updated:** 9 Feb 2026
- **Also known as:** GHSA-46hm-9585-gfr6

## What is CVE-2026-1727?

CVE-2026-1727 is a critical vulnerability in Google Cloud Gemini Enterprise (formerly Agentspace), published on 6 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-1727?


## How do I fix CVE-2026-1727?

No fix has been published for CVE-2026-1727 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-1727 being exploited?

There is no known exploitation of CVE-2026-1727 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1727 and fix it if it is affected.

What it is: CVE-2026-1727 is a critical vulnerability in Google Cloud Gemini Enterprise (formerly Agentspace), published on 6 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-1727 in the wild and no public exploit code.

Affected product: Google Cloud Gemini Enterprise (formerly Agentspace). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-1727/ (Markdown: https://insights.sbomify.com/CVE-2026-1727/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1727
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1727
- OSV: https://osv.dev/vulnerability/CVE-2026-1727

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1727/
Summaries are generated and may contain mistakes; the official description above is the record.