Latest / Decrypted: The UK Cyber Briefing / Supabase's secure default skips the way most apps are built now
Transcript
- 0:03This is Decrypted. Tuesday, the twenty-ninth of September.
- 0:08Supabase's secure default skips the way most apps are built now.
- 0:13Sixteen thousand, three hundred and twenty six leaking databases.
- 0:18It sounds like a story about careless developers.
- 0:21It's really a story about a lock that only fits one door.
- 0:25Researchers at UpGuard scanned roughly 300,000 domains built on Supabase, the database platform behind a larg
- 0:34e share of today's AI-assisted app building.
- 0:37They found that many of the exposed tables were leaking real personal data: names, tokens, and in a Canadian
- 0:45immigration service's case, 884 plaintext passwords.
- 0:50The telling detail isn't that developers made mistakes.
- 0:54It's that Supabase's own security default only switches on if you build a table one particular way.
- 1:01And the way most people now build tables is the other one.
- 1:05Next.
- 1:11Supabase controls access through something called Row Level Security, or R L S.
- 1:18It's a policy layer that decides which rows a given key is allowed to see.
- 1:23Since 2025, Supabase has switched R L S on by default for any table created through its Table Editor, the poi
- 1:32nt-and-click web console. But tables created programmatically, through the A P I, don't get R L S switched on
- 1:40by default.
- 1:49database. Someone types "build me a booking system" into a chat window.
- 1:55The agent calls the A P I, the table appears, and the safety switch that would exist if a human had clicked t
- 2:02hrough the console is simply absent.
- 2:04Now add the habit of pasting a "public" anonymous key into client-side code as though it were a secret one.
- 2:12Any table without R L S is then readable by anyone who finds that key sitting in the page source.
- 2:19That's most of them.
- 2:22Whose default is it, anyway.
- 2:25Vendors are right to say a default can't cover every configuration choice a developer might make.
- 2:31But this default fails on the single most common path in 2026: code that a person never directly wrote.
- 2:39UpGuard's own framing is the sharpest part of its report.
- 2:43It argues it's "time to rebalance the equation", the way Amazon did with S3, which flipped to private-by-defa
- 2:51ult buckets after a decade of leaks, and the way GitHub did with new repositories.
- 2:56A secure default that quietly exempts the fastest-growing way of using a product isn't a default.
- 3:03It's a footnote.
- 3:06What UK organisations should take from this.
- 3:09Plenty of UK fintechs, agencies and startups are prototyping on Supabase, often through exactly the AI tooli
- 3:17ng this report describes. And they're moving those prototypes into production faster than anyone reviews them.
- 3:24A misconfigured database holding customer P I I is a personal data breach under UK G D P R.
- 3:32It doesn't matter whether it was built by a contractor or a chatbot.
- 3:36"The AI did it" is not a defence the I C O has ever accepted, and there's no reason to expect it to start.
- 3:44The practical fix costs little.
- 3:46Before anything built this way goes live, someone should run Supabase's own security advisor.
- 3:53They should confirm R L S is enabled on every table.
- 3:57And they should treat an anonymous key found in client-side code as a red flag, not normal practice.
- 4:03Secure by Design was written for humans writing code by hand.
- 4:08It has to survive the case where nobody did.
- 4:11That was Decrypted. The written version and every source are linked in the show notes.
- 4:16Thanks for listening.