CVE-2026-12715
Firebase Studio could expose another tenant’s deployment source code
Google Cloud · Firebase Studio
First documented disclosure · Review checkpoint
Summary
A signed-in Firebase Studio user could obtain deployment source code belonging to another tenant.
Severity and exploitation evidence
High · 8.5/10 · CVSS 4.0. Severity source.
Exploitation not established: Google documented a vulnerability and a correction. The reviewed sources identify no exploitation against customer environments.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
The service granted access to stored deployment files without adequately checking their tenant owner.
Conditions required
An authenticated Firebase Studio user had access to the affected hosted service.
Potential impact
Private source code and sensitive values stored with it could be exposed.
Affected versions and configurations
The Google CNA lists the hosted service before April 15, 2026.
Fix and mitigation status
Google deployed a backend fix. The CNA uses April 15, 2026 as the affected-version cutoff.
Practical next steps
Review sensitive values formerly stored in affected workspaces. Google advises that customers may rotate those keys as a precaution.
Operating lesson
Verify tenant ownership before granting access to stored deployment artifacts.
Evidence and limits
Google announced the issue June 24. The CNA published its record July 17. The service fix predates both dates.
Sources
- Google Cloud security bulletin GCP-2026-043
Primary source ·
- Google Cloud CVE authority record
Primary source ·