Skip to main content
ShipSafe
4 out of 5 Bolt.new projects have critical vulnerabilities

Security Scanner forBolt.new Apps

Bolt.new ships full-stack apps in seconds. But unauthenticated API routes and exposed secrets mean your app could be compromised in seconds too. ShipSafe finds what Bolt's AI missed.

Free scan2 minutesNo card needed

The short answer

The Security Cost of Instant Full-Stack Apps

Bolt.new is impressive. You describe what you want, and it generates a complete application with frontend, backend, and database in one shot. The problem is that the AI skips the boring but critical security plumbing that separates a demo from a production app.

Every API route Bolt creates is a potential entry point for attackers. Without auth checks, anyone can call them. Without input validation, malicious payloads flow straight through. And because Bolt uses Vite, any secret prefixed with VITE_ ends up in your users' browsers.

We've documented the specific patterns in our Bolt.new security guide and the vulnerabilities by platform reference.

Common vulnerabilities

Common Vulnerabilities in Bolt.new Projects

These patterns appear in the vast majority of Bolt.new-generated applications we analyze.

  1. Unauthenticated API Routes

    Critical

    Bolt.new generates API endpoints that handle data mutations (create, update, delete) without verifying that the caller is logged in. Anyone who discovers the route can call it directly with curl or Postman, bypassing your entire frontend.

  2. Secrets in VITE_ Environment Variables

    Critical

    Bolt.new uses Vite as its build tool, and any env var prefixed with VITE_ gets bundled into the frontend JavaScript. The AI frequently puts API keys, database URLs, and webhook secrets behind VITE_ prefixes, making them visible to anyone who opens browser DevTools.

  3. Missing Input Validation

    High

    Bolt-generated endpoints typically trust all incoming data. There is no schema validation, no type checking, and no sanitization. Malformed payloads, oversized inputs, and injection attempts pass straight through to your database.

  4. No CSRF Protection

    High

    Bolt.new does not generate CSRF tokens or SameSite cookie configurations. State-changing requests can be triggered from any website by embedding a hidden form, letting attackers perform actions on behalf of logged-in users.

How ShipSafe Secures Your Bolt.new App

1

Connect Your Bolt.new Project

Link your GitHub repo or paste your source code. ShipSafe recognizes Bolt.new's Vite-based project structure and understands how it handles routing and env vars.

2

Full-Stack Security Analysis

ShipSafe scans both frontend and backend code. It maps every API route, checks for auth middleware, validates env var scoping, and tests for CSRF and input validation gaps.

3

Prioritized Fix Guide

Receive a severity-ranked report with concrete code examples showing exactly what to change. Copy-paste the fixes directly into your Bolt.new project.

Frequently Asked Questions

Is Your Bolt.new App Actually Secure?

4 out of 5 Bolt.new projects we scan have a critical vulnerability. 2 minutes to find out if yours is one of them.

Scan My Bolt.new App Free

No credit card required. See all plans

.env — bolt.new
1VITE_STRIPE_SECRET_KEY=sk_live_51N…aQpZ
2VITE_OPENAI_API_KEY=sk-proj-9d4f…0c12
3VITE_DATABASE_URL=postgres://u:p@db.acme.io/main

Anything prefixed VITE_ ships to every user's browser. These are not secrets — they're public strings that happen to unlock your Stripe account.