Lovable Bakes Auto Security Scanning Into Every App You Publish

Lovable now runs an automatic 10-15 second security scan before every publish, with optional deep AI reviews and an opt-in agent that fixes findings for you.

·
·
·

Vibe coding platforms have a security problem, and Lovable has been at the center of it. Now the company is trying to make safety a default rather than an afterthought. Lovable shipped a new security experience that runs a scan automatically every time you hit publish, with an optional AI agent that quietly fixes problems as you keep building.

According to Lovable, a basic security scan now runs automatically every time you publish, covering database configurations, RLS policies, and cloud project settings in about 10 to 15 seconds. It runs for everyone, whether you ask for it or not.

What the scan actually checks

When you click publish, the scan kicks off in the background. In about 10 to 15 seconds, it checks for the most common and impactful issues: database misconfigurations, missing RLS policies, and authorization gaps.

RLS, or Row Level Security, is the access-control system in Postgres databases that decides which rows of data each user can see or change. Get it wrong and anyone with your public API key can read your entire database.

By the time the publish dialog finishes loading, you see one of three outcomes: the scan passed, warnings were found, or critical issues were found. If you or your workspace admin enabled publish blocking, you must fix the critical ones first. Publish blocking is an Enterprise-only gate.

A second tier handles deeper coverage. The basic scan does not analyze application code for logic flaws or vulnerabilities unique to how your app is built. That falls to the deep security scan, a full AI-powered review of your codebase that completes in roughly three minutes. Lovable recommends running one when you are preparing to launch publicly, handling sensitive user data, or making significant architectural changes. Dependency checks run behind the scenes on every edit you make to application dependencies, so supply chain security stays continuously monitored.

The agent that fixes things while you work

The most interesting part is auto-fix, an opt-in feature that turns findings into actual code changes. Lovable scans your app and flags findings during the first publishing flow, then, as you keep building, the agent resolves straightforward, low-risk issues as part of your regular prompts. The agent only attempts non-breaking changes, meaning nothing that could alter how your app behaves.

A memory layer makes the scanner less annoying over time. When you dismiss, accept, or provide context on a finding, the agent remembers, building a model of your project's security profile that both the scanner and the coding agent reference. You can edit that security memory directly. In Lovable's testing, security memory reduced ignored findings by about 20 percent and increased scanning accuracy.

Pricing and who it is for

The baseline is free for everyone. Auto-fix is available as an opt-in feature across all plans through workspace settings. The heavier governance features sit behind paid tiers: workspace admins can block publishing on critical findings, and Business and Enterprise workspaces can schedule recurring deep scans across all projects on a weekly or monthly cadence.

The target users break down cleanly:

  • Solo builders who do not need to know what RLS policies are or how to audit a database.
  • Teams and admins who can enable auto-fix at the org level so the baseline rises across every project at once.
  • Enterprise customers who get the fast basic scan as the default publish gate, replacing the old multi-minute scan, plus scheduled deep scans so nothing falls through the cracks.

Why this release matters

Lovable has shipped a security scanner before, and that history is the real context. Security researcher Matt Palmer disclosed CVE-2025-48757, and his tests retrieved emails, phone numbers, payment details, API keys, and other personal information from vulnerable endpoints across at least 170 Lovable-built apps. The first scanner Lovable shipped in response drew sharp criticism because it only flagged the presence of RLS, not whether it worked, missing misconfigured policies and creating a false sense of security.

That history sets the bar this release has to clear. Independent scanners that probe live apps flag a recurring trap: RLS enabled with no policies returns zero rows even to logged-in users, so developers add a permissive policy to make the app work, which effectively disables RLS. Lovable's own AI has been observed doing exactly this. Whether the new scan catches that class of misconfiguration, rather than just checking that a policy exists, determines whether this is a genuine fix or a faster version of the old one.

The structural bet is sound. Most AI-generated app vulnerabilities are predictable and consistent, which makes them scannable in a single automated pass. By wiring that pass directly into the publish flow and letting an agent remediate safe findings, Lovable treats security as part of the build loop. For a platform whose users explicitly do not want to learn database access control, baking the check in by default is the only version of security that actually gets used.

Trending
  • No trending articles

Comments

avatar

Next Reads