CVE-2026-12715
Auth bypass in Firebase Studio allowed unauthorized download of deployed source code.
Is CVE-2026-12715 being exploited?
Not confirmed. CVE-2026-12715 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.35% probability of exploitation in the next 30 days.
How severe is CVE-2026-12715?
CVE-2026-12715 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-12715?
Yes. A fix has been recorded for CVE-2026-12715. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-12715 affect?
CVE-2026-12715 affects Google Cloud Firebase Studio (versions prior to 2026-04-15), GCP projects using Firebase Studio, Deployed Firebase app source in GCS buckets. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-12715?
Confirm Firebase Studio updated to 2026-04-15+; review access logs and rotate any exposed secrets.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers could download other users' deployed source code and access sensitive data via unauthorized GCS URL signing requests.
Monitor only
- affected< 2026-04-15
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.