1007 points by armcat 6 days ago | 382 comments | View on ycombinator
neathack 6 days ago |
igorandri 6 days ago |
When an app has end users, security is a key part of the product. That’s why we keep investing in making security tools better and easier to use, taking on as much of the security load as we can and fixing more issues automatically.
I personally believe that making security accessible is what leads to making software accessible. We’re committed to both.
You can read more about our approach: https://lovable.dev/blog/find-it-fix-it-ship-it
SOLAR_FIELDS 6 days ago |
This was supposedly fixed on October 30, but there are reports floating around that for existing projects, the defaults still apply.
Lovable deserves some heat for using this, but this was a choice that was made by Supabase many years ago to support making it easier to onboard potential customers, a deliberate tradeoff of less onboarding pain for less security.
yakkomajuri 5 days ago |
In this case we're talking about vibe coders, who don't know about the implementation details. But we've gotten here in the first place because a lot of developers adopted this Supabase RLS serverless model. I always found it surprising that this model stuck.
adverbly 6 days ago |
Allowing anyone to build and host a public app without a basic understanding of these things is like letting people fly a passenger plane without a license.
Oras 6 days ago |
- They are an easy target, they don’t need any sophisticated hacking knowledge (article mentions inspecting network calls in browsers).
- There tons of those, and more created everyday. For the average user, they don’t know what they are using, or how risky it can be.
liquid_thyme 6 days ago |
nospi 6 days ago |
Can someone please correct me if I'm wrong here, but isn't the article claiming that all data was publicly accessible with a read-only API key, also publicly shipped in each site?
Unless I'm missing something, no amount of digging into *published* data is a breach of anything. The act of publishing it is the leak, not the consumption.
Am I losing the plot?
xyst 6 days ago |
But unfortunately, it’s not always this transparent. In the US, doctors (particularly PE owned ones) often use AI in their backend in one form or the other. In one case, I observed their transcription service was using some LLM to help process data into medical record.
In other cases, your data may even be processed/leaked/trained without your explicit consent through a third party vendor that doesn’t interact directly with doctors office (physician office -> order sent to pharmacy -> pharmacy uses LLM to process data).
This is at least the case for the insidious CVS/Caremark conglomerate.
guestlistplus10 6 days ago |
IceDane 5 days ago |
I would say that something like 3/4 supabase projects that are submitted have issues like this. The latest i found was exposing health-related data.
Supabase is positioned similarly to firebase: you don't need a separate backend, and you access your database directly from the frontend. Security is dependent on relatively complicated rules in your database (simpler for firebase, a lot more involved for supabase with RLS)
This means it's a tool that is frequently reached for by newbies - the same sort of people who are the worst equipped to actually implement these complicated security rules themselves. With the advent of vibecoding, many people building are almost entirely dependent on the AI doing the right thing in every case. And this will get progressively more complicated to do correctly the more complicated the schema and usage patterns become.
I think we are in a territory where it is borderline irresponsible for supabase.
hn_throwaway_99 6 days ago |
The defects listed in this report didn't require some complicated 0-day exploit chain - they were just sensitive data stored without any authentication at all, in a database that anyone with Internet access can view. In other words, it would be the equivalent of a company like Public Storage leaving all of its storage units with no locks on them at all.
Affected users should be able to sue for a lot in these basic security failures. And obviously for many of these small websites, the potential damages would quickly bankrupt the site owners, but that's the point. People would think a lot more carefully about how they protect sensitive data if there were real negative consequences for their failures.
system2 5 days ago |
munishjindal931 1 day ago |
alorenzom 5 days ago |
YuechenLi 6 days ago |
To me, it feels like Lovable is an irresponsible product selling the idea that web development is trivial now with LLMs, where the reality is that although it's true that agentic coding means while anybody can spin up a website in like 10 minutes, a professional software engineer who knows what they are doing can still utilize LLMs much more effectively than an amateur ever could.
gregman1 6 days ago |
berkes 6 days ago |
redanddead 6 days ago |
ArchEagle 5 days ago |
rNULLED 6 days ago |
birdsongs 6 days ago |
Nearly two decades of experience learning how to build safe, performant software, to be replaced by this shit.
We don't care about people, our customers anymore. We actively harm them for profit. This is such a garbage industry now.
arunakt 5 days ago |
sooraj_sj 5 days ago |
newmean-ai 4 days ago |
Paaul01 3 days ago |
polymodality 3 days ago |
node1ai 5 days ago |
edekozar 5 days ago |
sitein48 4 days ago |
igorandri 6 days ago |
sarah_reid 5 days ago |
NorthSouthNorth 6 days ago |
Like mentioned elsewhere in this thread, there are doctors vibe coding shite and sending private medical data to Anthropic's servers, probably without even checking the "don't use for training lol" checkbox. Thousands of passports, invoices, whatever, are rn available on the open internet. People posting private company data on PUBLIC github repos (dealt with 2 such cases lol).
These individuals aren't held to the same standards, and right now nobody is enforcing the rules on them.
And maybe that's fine. Maybe we don't want to stifle innovation. But if my passport ends up on the dark web and I get identity theft'd, then I'd be pissed. There are REAL consequences.
nalekberov 5 days ago |
https://www.theregister.com/software/2026/02/27/ai-built-app...
aussieguy1234 6 days ago |
If your app processes personal info, even if it's just a "sign up with your email to keep updated" list on a landing page, it needs proper security
rvz 6 days ago |
Imagine frontier abliterated models running at 2,400 TPS finding all these issues rapidly on web apps like this.
You are not ready security-wise when these models get faster. ("Formal verification" won't save you either)
ydna404 6 days ago |
Oh boy, open season on those entry points
testtestmetest 6 days ago |
undefined 6 days ago |
m00dy 5 days ago |
Leynos 6 days ago |
undefined 5 days ago |
pumba_noob 5 days ago |
yoy0721 5 days ago |
fastoolster 5 days ago |
rostig 5 days ago |
spencerawlson 5 days ago |
luc-lightscale- 5 days ago |
kushalpatel7 6 days ago |
sitein48 5 days ago |
nightmoose 5 days ago |
ankur_misra 5 days ago |
normanburdges 5 days ago |
ne01 5 days ago |
edekozar 5 days ago |
Pastookh 5 days ago |
agnosticatom 6 days ago |
musclehed03 5 days ago |
mlt22 5 days ago |
JustRouzbeh 5 days ago |
CatlinoMintern 5 days ago |
ahmedketata 6 days ago |
rumburak 6 days ago |
Recline 6 days ago |