Re:I Found 39 Algolia Admin Keys Exposed Across Open Source ...
by tcbrah on Friday March 13, 2026 @10:34PM
(#47372720)
the wildest part is algolia just not responding. you email them saying "hey 39 of your customers have admin keys in their frontend" and they ghost you? thats way worse than the keys themselves imo. like the whole point of docsearch is they manage the crawling FOR you, but then the "run your own crawler" docs basically hand you a footgun with zero guardrails. they could just... not issue admin-scoped keys through that flow
[ Parent
| on HN ]
Re:I Found 39 Algolia Admin Keys Exposed Across Open Source ...
by gregoriol on Saturday March 14, 2026 @03:29AM
(#47374219)
What contact Algolia when its the users responsibility to handle their keys? Contact all the users.
Re:I Found 39 Algolia Admin Keys Exposed Across Open Source ...
by Kwpolska on Saturday March 14, 2026 @06:08AM
(#47375098)
If this happens so often, perhaps Algolia should improve their stuff to prevent this? For example, by implementing a dedicated search endpoint that doesn't accept normal API keys, but only dedicated read-only keys.
Re:I Found 39 Algolia Admin Keys Exposed Across Open Source ...
by interstice on Saturday March 14, 2026 @07:18AM
(#47375510)
It is the users responsibility to operate foot guns responsibly.
Re:I Found 39 Algolia Admin Keys Exposed Across Open Source ...
by jgalt212 on Saturday March 14, 2026 @08:51AM
(#47376165)
because if it's easy to dangerously use one's product that reflect poorly on the product. Algolia should help its clients from making silly mistakes.
Re:I Found 39 Algolia Admin Keys Exposed Across Open Source ...
by pwdisswordfishy on Saturday March 14, 2026 @10:10AM
(#47376870)
The comment you're responding to is output of an LLM.