A vibe-coding platform sat on a critical vulnerability for 48 days after closing the bug report — what founders using AI app builders need to take from it

A Broken Object Level Authorisation flaw in Lovable, the $6.6bn vibe-coding platform, let anyone with a free account read another user's source code, database credentials and customer data using five API calls — and stayed exploitable for 48 days after a researcher's HackerOne report was closed without escalation.

A security researcher filed a HackerOne report against Lovable, the $6.6bn vibe-coding platform, on 3 March 2026. Lovable closed it without escalation, citing “outdated internal documentation” given to the triage team. The underlying flaw — a Broken Object Level Authorisation (BOLA) bug in Lovable’s API — meant anyone with a free account could read another user’s source code, database credentials, AI chat history and customer data with as few as five API calls. It affected every project built on the platform before November 2025 and stayed exploitable for 48 days after the report was first filed.

This is the third documented security incident tied to Lovable, and it lands alongside a wider pattern: researchers have found comparable authorisation failures across other vibe-coding platforms this year, including a platform-wide authentication bypass on Base44 and a zero-click remote-code-execution bug on Orchids. Industry-wide testing puts the rate of AI-generated code shipping with at least one security flaw at 40–62%, and one 2026 study found 91.5% of vibe-coded apps had at least one hallucination-related flaw.

The structural problem, not just the bug

What makes the Lovable case worth flagging isn’t the vulnerability class — BOLA bugs are common and well understood — it’s the disclosure failure. Lovable had no audit trail to detect that a closed, “fixed” report was still being actively exploitable, and no process that could catch the gap once the bug bounty channel had already failed once. That’s a governance problem, not a coding problem, and it’s specific to platforms where a huge number of independently built apps share one underlying authorisation layer: a single missed fix doesn’t affect one product, it potentially affects every project the platform has ever hosted.

So what

If you or your team have built anything commercially important on a no-code or AI app-builder platform, this is worth an honest audit: what happens to your product, your users’ data, and your reputation if the platform’s shared infrastructure has a flaw like this one — and how would you even find out? It’s a fair question to put to any platform vendor, and a fair reason to move a product from prototype to a properly engineered, independently reviewed codebase once it’s carrying real user data or real revenue. Our custom software development work is built for exactly that transition — get in touch if you’re weighing whether your product has outgrown its builder.

← All research

More research.

GitHub secret scanning cuts false alarms for AWS, Google and Alibaba cloud keys and adds a SpaceX detector

GitHub's 5 November 2026 secret scanning update tightens detectors for AWS, Google Cloud and Alibaba keys, relevant to teams building software with AI coding tools that can paste credentials into code.

Read ›

GitHub's Copilot code review can now be managed by API, with review effort levels and AI credit costs shown

GitHub's 6 November 2026 update lets organisations manage Copilot code review by API and see the review effort and AI credits each AI code review used, a sign AI-assisted development is becoming auditable.

Read ›

GitHub's Copilot impact dashboard now counts chat and VS Code agent use, and drops the 'passive users' label

On 6 November 2026 GitHub added Copilot Chat and the VS Code Agents window to its Copilot impact dashboard, bringing it to nine tracked experiences, and renamed 'Passive users' to 'Chat-first users'.

Read ›

Claude Code 2.1.319: a setting that denies permission prompts so AI agent runs don't stall

Claude Code 2.1.319 (6 November 2026) adds a permissions.denyInsteadOfPrompting setting and moves long MCP tool calls to the background, a sign AI-assisted development is being built for unattended runs.

Read ›

GitHub now reports how often developers act on Copilot code review comments

On 5 November 2026 GitHub added code review metrics, including an addressed rate, to the Copilot usage metrics API. For AI software development buyers, it is the first first-party number for how much AI review feedback is acted on.

Read ›

Dependabot can now keep AI agent skills and prompts up to date

GitHub's Dependabot gained Agent Package Manager (APM) support on 3 November 2026, treating AI agent skills, prompts and instructions as dependencies that need updating like any other software.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work