Google API Keys Weren't Secrets. But then Gemini Changed the Rules.
Summary
Google API keys that were originally created as public identifiers for Google Maps became dangerous security risks when Google enabled the Gemini API on the same projects, because Gemini keys can access private files and make billable requests, yet developers were never notified of this privilege change. Truffle Security discovered nearly 3,000 exposed API keys in web archives that could access Gemini, including some belonging to Google itself, highlighting how a service upgrade unexpectedly transformed harmless public keys into secret credentials.
Solution / Mitigation
Google is working to revoke affected keys. Additionally, Google recommends checking your own API keys to verify none of yours are affected by this issue.
Classification
Affected Vendors
Related Issues
CVE-2025-45150: Insecure permissions in LangChain-ChatGLM-Webui commit ef829 allows attackers to arbitrarily view and download sensitive
CVE-2025-54868: LibreChat is a ChatGPT clone with additional features. In versions 0.0.6 through 0.7.7-rc1, an exposed testing endpoint
Original source: https://simonwillison.net/2026/Feb/26/google-api-keys/#atom-everything
First tracked: February 26, 2026 at 03:00 AM
Classified by LLM (prompt v3) · confidence: 92%