Netlify
Security FAQ

What security issues do Netlify apps have?

Get instant answers about your app's security.

Short Answer

Netlify apps surface a predictable distribution of issues: 1 critical-impact class (build-time secret exposure), 0 high-impact, 4 medium-or-below. The critical ones are what cause data breaches.

Detailed Answer

Critical issues in Netlify apps

  • **Build-Time Secret Exposure**: Build-time env vars get baked into static HTML, visible to anyone.

Medium/low-severity issues

  • **Deploy Preview Exposure**: Preview deployments expose unreleased features publicly.
  • **Missing _headers File**: Security headers not configured by default.
  • **Form Spam Without Protection**: Netlify Forms are public endpoints vulnerable to spam.
  • **Function Timeout Attacks**: 10s timeout (26s paid) can be exploited for resource exhaustion.

Why these are the issues specific to Netlify

Netlify apps ship with a recognizable stack (supabase, firebase). The issue list above is what appears when you scan that specific combination. A Firebase-backed app would have a different top-5; a self-hosted Postgres deployment would have yet another. Context is everything.

What VAS checks in a Netlify scan

  • **Environment Config** — Review environment variable setup.
  • **Functions Security** — Check serverless function security.
  • **Headers Setup** — Verify _headers file configuration.
  • **Form Security** — Check form handling and spam protection.

Security Research & Statistics

10.3%

of Lovable applications (170 out of 1,645) had exposed user data in the CVE-2025-48757 incident

Source: CVE-2025-48757 security advisory

4.45 million USD

average cost of a data breach in 2023

Source: IBM Cost of a Data Breach Report 2023

500,000+

developers using vibe coding platforms like Lovable, Bolt, and Replit

Source: Combined platform statistics 2024-2025

Expert Perspectives

Vibe coding your way to a production codebase is clearly risky. Most of the work we do as software engineers involves evolving existing systems, where the quality and understandability of the underlying code is crucial.

Simon WillisonSecurity Researcher, Django Co-creator

The problem with AI-generated code isn't that it doesn't work - it's that it works just well enough to ship, but contains subtle security flaws that are hard to spot.

Security Research CommunityCollective wisdom from security researchers

Check Your Netlify App's Security

VAS scans for all the security issues mentioned above. Get a comprehensive security report in minutes.

Get Starter Scan

More Questions About This Topic

Which Netlify security issue is most dangerous?

Build-Time Secret Exposure. Build-time env vars get baked into static HTML, visible to anyone. This is the highest-impact finding because it tends to expose the full dataset or grant lateral movement in one step. The fix: Use Netlify Functions for runtime secrets. Never build-time for secrets.

Are these issues unique to Netlify, or do they appear across platforms?

The patterns overlap with vercel, railway, render — all vibe-coding platforms share the "AI-generated code prioritizes functionality over security" problem. But the *specific manifestation* differs per platform. An exposed Supabase anon key is structurally different from an exposed Firebase config, which is different from an exposed Postgres connection string. The right scan is platform-aware.

How do I see which of these issues my Netlify app has?

Run a VAS scan against your deployed Netlify app URL. It checks every issue in the list above, confirms each by actually probing (not just reading headers), and prioritizes by severity with copy-paste fixes. Most Netlify app scans return results in 2–3 minutes.