Algolia Security Incident: What BigCommerce Stores Must Do
No7 Engineering Team
Growth Architecture Unit

The Algolia security incident is a breach of systems at Algolia, the search company. BigCommerce says it may have exposed the keys that the Algolia app holds for merchant stores. Algolia told BigCommerce on 18 November 2026. BigCommerce has now emailed stores that use the app and asked them to act. The first step is to uninstall the Algolia app, which cuts off the access the app was given.
We found no public statement from Algolia or BigCommerce when this post went live on 20 November 2026. This post is based on the notice BigCommerce sent to merchants, which No7 Software has seen. The how-to steps come from Algolia and BigCommerce docs, which we link to. Where a fact is not known yet, we say so.
What happened in the Algolia security incident?
The notice is signed by the Commerce Security Team. Commerce is the name of the parent company of BigCommerce. The notice says Algolia reported a security incident in its own systems on 18 November 2026. For BigCommerce stores, two things held by Algolia may be exposed. One is the set of credentials for the Algolia app. The other is the store access tokens of merchants.
BigCommerce says it knows of no breach of its own platform. It sends questions about the cause, and about the data involved, to Algolia.
A store access token is the key an app gets when a merchant installs it. It lets the app call the store API with the rights the merchant agreed to. The BigCommerce developer docs describe it as a semi-permanent access token, so it does not run out after a few hours. Anyone who holds a valid token can make the same calls as the app.
Algolia is a hosted search service. On BigCommerce, its app sends your product data to Algolia and runs the search box, the search results page and product suggestions on your shop.
Who is affected?
The notice went to BigCommerce stores that use the Algolia app. If you got it, treat your store as in scope. If you use Algolia on BigCommerce and did not get it, check the inbox of the store owner. Then ask Algolia.
| Question | What the notice says |
|---|---|
| Whose systems were breached? | Those of Algolia. BigCommerce reports no known breach of its own platform. |
| What may be exposed? | Algolia app credentials and merchant store access tokens held by Algolia. |
| When was BigCommerce told? | 18 November 2026. |
| What data was taken from my store? | Not stated. BigCommerce tells merchants to ask Algolia what it found for their account. |
| Are Algolia apps on other platforms hit? | Not stated. The notice covers BigCommerce only. |
What should BigCommerce merchants do now?
The notice lists five actions. You can skip any that you have already done after hearing from Algolia.
- Uninstall the Algolia app. BigCommerce says this removes the access that the exposed credentials had to the platform. It warns that site search may stop until you connect the app again.
- Revoke the old Algolia Search API key. The notice says a fresh install does not do this for you. You have to do it by hand, in Algolia and not in BigCommerce.
- Ask Algolia about your store. Read anything Algolia has sent you. Then ask its support team, or your account manager, what they found for your account.
- Review your store activity. Look for access or changes you did not expect. Ask Algolia which dates you need to check. BigCommerce says it can help with the app removal and with the platform logs it has.
- Check your duty to notify. The notice says to ask your legal, privacy or compliance advisers. They can judge whether you need to look further or tell anyone, based on what Algolia finds.
Why remove the app and not just swap the token? The BigCommerce guide to API accounts says there is no way to revoke an app access token by hand. It also says each install makes a new token for that store. So a clean removal and a new install is the way to get a fresh one. That link between the two is our reading of the docs. It is not a line from the notice.
How do you revoke the old Algolia API key?
The Algolia Search API key is the key your shop uses to run searches on your Algolia data. The notice names the Search API key tied to your BigCommerce set-up as the one to revoke.
The Algolia guide to API keys says that revoking a key makes it unusable. You revoke a main key by deleting it in the Algolia dashboard, or with the deleteApiKey method. The same guide says that if a key is leaked, you should revoke it as soon as you can.
What could a stranger do with an old search key? The guide lists two risks for a search-only key in the wrong hands. They could copy everything in your indexes. They could also flood your account with search requests. For example, a rival could pull your full product list and prices in one go.
One more point. Algolia can restore a deleted key. Do not restore the old one later, even if a theme or script still asks for it. Give that script the new key.
How to uninstall Algolia from BigCommerce cleanly
The Algolia uninstall guide for BigCommerce gives an order of steps. Follow it and you will not leave widgets or metafields behind.
- If InstantSearch Categories is on for a channel, turn it off under Search experience in the Algolia app. If you skip this, unused metafields may stay on your store.
- If Recommendations is on for a channel, turn it off in the same place. If you skip this, the widget template may stay on your store.
- In the app, go to Settings and select Disconnect. Algolia says this removes all indexes and stops search on your shop.
- Uninstall the app in BigCommerce.
The guide adds a point that matters here. The uninstall removes the sync tasks and the shop parts of the app. It keeps the API keys the app made in your Algolia account. You have to delete those in the Algolia dashboard. That fits the warning in the notice that a new install does not revoke the old key.
What happens to site search while the app is removed?
Your shop stops using Algolia for search once the app is disconnected. Plan for that before you start, above all in the run-up to Black Friday.
- Check what search falls back to. Test the search box right after the uninstall, so you know what shoppers see.
- List what the app runs. Search results pages, category pages, autocomplete and product suggestions can all depend on it.
- Do not skip the uninstall to avoid a gap. BigCommerce presents the uninstall as the way to cut off the exposed credentials. A short gap in search is the smaller risk.
Before you reconnect Algolia
BigCommerce says a new install, done the way Algolia tells you, gives the app a newly issued access token. It also asks merchants to think first. Does the app still meet your security, privacy, compliance and day-to-day needs?
- Wait for the findings from Algolia if you can, so you know what you are connecting to.
- Delete the old API keys in the Algolia dashboard before the new install, or right after it.
- Look at the rights the app asks for when you install it again. Ask whether each one is needed.
- Check who can log in to your Algolia account. The Algolia security best practices say every user should turn on two-factor authentication. They also say to renew all API keys at least once a year.
- Do the same for your store staff. CISA, the US cyber agency, has a short guide on how to turn on MFA.
What is not known yet
- How the systems at Algolia were breached, and when.
- Whether the exposed tokens were used against any store.
- How many BigCommerce stores are in scope.
- Whether Algolia apps for other platforms, such as Shopify or Adobe Commerce, are hit. The notice we have seen covers BigCommerce only, so we draw no conclusion either way.
We will add a dated update to this post when Algolia or BigCommerce says more.
Why app tokens are a weak point in BigCommerce security
You can guard your own store login with a strong password and a second step. But every app you install holds its own long-lived key to your store, on the servers of another company. When that company is breached, your store is exposed, and nothing in the store itself was broken into.
This is a supply chain risk. The UK National Cyber Security Centre has supply chain security guidance built on 12 principles. The first group is about knowing the risks your suppliers bring. We saw the same pattern in the Shopify checkout hijack through compromised apps. Shopify is now moving apps to tokens that expire and to IP allowlists.
Keep a list of the apps on your store. Remove the ones you no longer use. Know which of them can read customer and order data.
Sources and methodology
This post sums up a notice that BigCommerce sent to merchants who use the Algolia app. No7 Software saw it on 20 November 2026. Fact check: every statement about the incident comes from that notice. The steps for keys, tokens and the uninstall come from the Algolia and BigCommerce docs linked above. We read each one on 20 November 2026.
On the same day we searched the public pages of Algolia and BigCommerce, the GitHub advisory database and the NVD. We found no public statement and no CVE for this incident. No7 Software is a BigCommerce Certified Partner. You can read more about us.
What to do next
If your BigCommerce store uses Algolia, uninstall the app today. Delete the old Algolia API keys. Ask Algolia what it found for your account. If you want help to check store activity, plan the search gap or reconnect the app safely, get in touch with our team. You can also see our BigCommerce development work.
Frequently Asked Questions
The questions buyers and engineers ask us most about this topic.
What is the Algolia security incident?
It is a compromise of systems at Algolia, the search provider. BigCommerce has told merchants that Algolia notified it on 18 November 2026, and that the potential impact for BigCommerce stores is Algolia app credentials and merchant store access tokens held in Algolia's environment.
Was BigCommerce hacked?
BigCommerce says there is no known impact on or compromise of its own systems or platform. The incident involves Algolia's systems, which held credentials and access tokens for stores that installed the Algolia app.
Do I need to uninstall the Algolia app from my BigCommerce store?
If you received BigCommerce's notice, yes. BigCommerce says uninstalling the app removes the platform access that the credentials in Algolia's compromised systems had. Site search and other features that run through the integration may stop until you reconnect.
Does reinstalling Algolia fix the problem?
Not fully. Reinstalling and reconnecting gives the integration a newly issued access token, but the notice says the previous Algolia Search API key is not revoked automatically. You need to revoke or delete it yourself in Algolia.
Was customer data stolen in the Algolia incident?
That has not been stated. BigCommerce's notice does not say what data was accessed and tells merchants to ask Algolia for account-specific findings, then take legal or privacy advice on any notification duties.
Does the Algolia incident affect Shopify stores?
It is not known. The notice No7 Software has seen was sent by BigCommerce and covers the BigCommerce integration only. Neither Algolia nor BigCommerce had published a public statement by 20 November 2026.
How do I uninstall Algolia from BigCommerce?
Algolia's documentation says to turn off InstantSearch Categories and Recommendations under Search experience, select Disconnect under Settings in the app, then uninstall the app in BigCommerce. Afterwards delete the API keys the integration created in the Algolia dashboard, because uninstalling keeps them.