<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>VibeGuard daily security tips</title><link>https://vibeguardscan.com/posts/</link><description>One short security tip a day for vibe-coded apps.</description><language>en</language><atom:link href="https://vibeguardscan.com/rss.xml" rel="self" type="application/rss+xml"/><lastBuildDate>Sat, 24 Oct 2026 04:00:00 GMT</lastBuildDate>
<item><title>The Lovable RLS hole: one missing policy exposed whole databases</title><link>https://vibeguardscan.com/posts/2026-10-24</link><guid isPermaLink="true">https://vibeguardscan.com/posts/2026-10-24</guid><pubDate>Sat, 24 Oct 2026 04:00:00 GMT</pubDate><description><![CDATA[<p>In 2025, researcher Matt Palmer found that many apps built with Lovable shipped without proper Row Level Security (RLS) on their Supabase tables. The result: anyone holding the public anon key, which sits in every page, could read or write whole tables. It was filed as <a href="https://nvd.nist.gov/vuln/detail/CVE-2025-48757">CVE-2025-48757</a>, rated 9.3 critical. Lovable disputes it, saying each app owner is responsible for their own data. Either way, the risk is yours.</p><p>Read <a href="https://mattpalmer.io/posts/CVE-2025-48757/">Palmer's write-up</a> for the details.</p><p><strong>Check yours today:</strong> open the Supabase Security Advisor, turn on RLS for every table in the <code>public</code> schema, and make sure no policy lets <code>anon</code> read every row.</p><p><a href="https://vibeguardscan.com/#scan">Scan your app free with VibeGuard</a></p>]]></description></item>
</channel></rss>
