Skip to main content
VulnerabilityPublished Updated

CVE-2026-1727: Google Cloud Gemini Enterprise (formerly Agentspace) · Information Exposure

Affects Google Cloud Gemini Enterprise (formerly Agentspace)Source CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical : upgrade to 12/12/2025 as a priority.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 12/12/2025
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Google Cloud Gemini Enterprise (formerly Agentspace) to 12/12/2025.

Affected software

ProductAffectedFixed in
Google CloudGemini Enterprise (formerly Agentspace)Affected
  • =0
Fixed in
  • 12/12/2025

AI-suggested

European organizations should immediately verify the version of Google Cloud Gemini Enterprise in use and ensure it is updated to a version released after December 12, 2025, where the vulnerability is patched. They should audit their Google Cloud Storage buckets to detect any unauthorized or suspicious buckets that may have been created via bucket squatting. Implement strict naming conventions and access controls for cloud storage resources to prevent predictability and unauthorized creation. Employ continuous monitoring and alerting for anomalous bucket creation or access patterns. Use Google Cloud's security features such as IAM policies, bucket policies, and organization policies to restrict bucket creation permissions to trusted administrators only. Conduct regular security assessments and penetration testing focused on cloud storage configurations. Additionally, review and enhance logging and alerting mechanisms to detect potential exploitation attempts early. Finally, educate cloud administrators about the risks of predictable resource naming and enforce best practices in cloud resource management.

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.

References

Community reviews

Loading reviews…