Virtual Event: CISO Forum Virtual Summit 2026 Day 2 - Join the Livestream
Connect with us

Hi, what are you looking for?

SecurityWeekSecurityWeek

Application Security

Leaked Algolia API Keys Exposed Data of Millions of Users

Threat detection firm CloudSEK has identified thousands of applications leaking Algolia API keys, and tens of applications with hardcoded admin secrets, which could allow attackers to steal the data of millions of users.

Threat detection firm CloudSEK has identified thousands of applications leaking Algolia API keys, and tens of applications with hardcoded admin secrets, which could allow attackers to steal the data of millions of users.

Organizations can use Algolia’s API to incorporate into their applications functions such as search, discovery, and recommendations. The API is used by over 11,000 companies, including Lacoste, Slack, Medium, and Zendesk.

CloudSEK says it has identified 1,550 applications that leaked Algolia API keys, including 32 apps that had hardcoded admin secrets, providing attackers with access to pre-defined Algolia API keys.

The offending 32 apps, CloudSEK says, had more than 2.5 million downloads, potentially exposing the data of their users to malicious attacks. A threat actor could exploit these weaknesses to read user information, including IP addresses, access details, and analytics data, and delete user information.

“While this is not a flaw in Algolia or other such services that provide integrations, it is evidence of how API keys are mishandled by app developers. So, it is up to individual companies to address the security concerns associated with payment gateways, AWS services, open firebases,” CloudSEK points out.

The Algolia API requires that the Application ID and API key are passed via two headers, to use services such as search, browse index, add records/delete records, list/update indexes, read/update index settings, and to retrieve logs and information from APIs.

Advertisement. Scroll to continue reading.

An attacker with access to the leaked API keys could access any of these features and read information they should not have access to.

CloudSEK points out that organizations should revoke the leaked API keys and generate new ones that are stored securely, and that authenticated endpoints should be used to communicate with sensitive, external APIs, to prevent the leak of secrets.

The company says it has informed both Algolia and the affected organizations of the hardcoded API keys.

Related: Thousands of Secret Keys Found in Leaked Samsung Source Code

Related: Researchers Find Tens of AWS APIs Leaking Sensitive Data

Related: Twitter Says Bug Leading to API Key Leak Patched

Written By

Ionut Arghire is an international correspondent for SecurityWeek.

Daily Briefing Newsletter

Subscribe to the SecurityWeek Email Briefing for the latest cybersecurity threats, trends, and expert insights.

Click to comment

You must be logged in to post a comment Login

Leave a Reply

Daily Briefing Newsletter

Subscribe to the SecurityWeek Email Briefing to stay informed on the latest threats, trends, and technology, along with insightful columns from industry experts.

NOW LIVE: CISO Forum 2026 Summit

Join as we bring together CISOs, senior cybersecurity executives, practitioners, industry experts, and other security leaders to share practical experience and examine the issues shaping enterprise cybersecurity strategy.

Register

Join to learn the four levels of architecting security into the agentic SDLC – from securing the code your developers' agents write to running a coordinated system of security agents you've built yourself.

Register

People on the Move

Tal Kapulnik has been named CMO at Terra Security.

Cloudflare has appointed Christian Smith as President of Revenue.

Doran Stienike has become CIO at Presidio.

More People On The Move

Expert Insights

Daily Briefing Newsletter

Subscribe to the SecurityWeek Email Briefing to stay informed on the latest cybersecurity news, threats, and expert insights. Unsubscribe at any time.