Skip to main content
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

Bolt can push your project to GitHub in a couple of clicks — connect that repo. 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 Bolt.new code secure?
Not by default. Bolt.new focuses on generating functional full-stack apps quickly, and security is consistently deprioritized. In our analysis, the most common issues are API routes without any authentication check, secrets exposed in the client bundle through VITE_ env vars, and a complete absence of input validation.
What security issues does Bolt.new create?
The four most frequent vulnerabilities are: (1) API routes that accept requests without verifying authentication, (2) sensitive secrets placed in VITE_ prefixed environment variables that get bundled into frontend code, (3) missing input validation on form submissions and API payloads, and (4) no CSRF protection on state-changing endpoints.
How do I secure my Bolt.new app?
Start by running a ShipSafe scan to identify all vulnerabilities. Then address them in priority order: add authentication middleware to every API route, move secrets to server-only env vars (remove the VITE_ prefix), add input validation using a library like Zod, and implement CSRF protection.
Does ShipSafe work with Bolt.new projects?
Yes. ShipSafe is specifically tuned to understand Bolt.new's project structure, including its Vite configuration, API route patterns, and environment variable handling. Bolt can push your project to GitHub in a couple of clicks — connect that repo and you're scanning.

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.

No credit card required. See all plans

This is an independent comparison provided for informational purposes. All product names, logos, and brands are the property of their respective owners; ShipSafe is not affiliated with, endorsed by, or sponsored by them. Statements about other products reflect publicly available information at the time of writing and may change, so please verify current details on each provider’s own website.

.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.