A critical Broken Object Level Authorization (BOLA) vulnerability in Lovable, the popular AI-powered app builder platform, reportedly allows unauthorized users to access sensitive project data, including source code, database credentials, AI chat histories, and real customer information, from thousands of projects created before November 2025.
The flaw enables any free-tier Lovable account holder to make unauthenticated API calls to the platform’s backend and retrieve project data belonging to other users.
BOLA vulnerabilities occur when an API grants access to objects without verifying whether the requesting user actually owns or has permission to view them. This is a class of flaw ranked #1 in the OWASP API Security Top 10 for its prevalence and ease of exploitation.
According to a researcher with the handle @weezerOSINT, the API endpoint https://api.lovable.dev/GetProjectMessagesOutputBody returns full project message histories, AI thinking logs, and tool-use records without enforcing proper object-level access controls.
The exposed JSON responses contain user IDs, session content, and internal AI reasoning chains that were never intended to be publicly accessible.
The vulnerability was reported to Lovable via HackerOne approximately 48 days before public disclosure, yet the flaw reportedly remains unpatched for projects created before November 2025.
While Lovable appears to have applied a fix for newly created projects, the legacy project base remains exposed, leaving a significant risk window for users who built applications on the platform before the cutoff date.
The Register reported that Lovable’s initial response attributed the exposed data to “intentional behavior” and “unclear documentation,” before shifting the blame to HackerOne. This move drew sharp criticism from the security community.
Researchers examining the vulnerability uncovered particularly alarming examples. One affected project belonged to Connected Women in AI, a nonprofit organization, which reportedly contained exposed Supabase database credentials alongside real user data.
Beyond nonprofit exposure, employees at major technology firms, including Nvidia, Microsoft, Uber, and Spotify, reportedly have Lovable accounts tied to affected projects, raising the potential that sensitive corporate development data could be at risk.
The vulnerability was submitted on the HackerOne bug bounty platform. It was marked as a duplicate of report #3583821, titled “Broken Object Level Authorization on Lovable API leads to unauthorized access to user data and project source code”.
The duplicate submission was flagged as Informative, suggesting the issue was already known to the platform before the March 3, 2026, disclosure, yet public evidence continues to show the flaw remains exploitable on legacy accounts.
Recommendations for Affected Users
Security researchers recommend that Lovable users who created projects before November 2025 take immediate action:
- Rotate all API keys, database credentials, and secrets stored within affected projects
- Assume chat histories and source code associated with older projects may have already been accessed
- Enforce secrets management practices independent of the platform, using dedicated vaults or environment variable managers.
- Regularly audit API exposure for any sensitive credentials embedded in project repositories or chat contexts
This incident underscores a recurring challenge in AI-native development platforms: security controls often lag behind rapid feature deployment, leaving early adopters most exposed.
Organizations building production applications on low-code AI builders should enforce defense-in-depth security strategies and not rely solely on platform-level protections.
This is at least the second significant security event tied to Lovable in 2026 alone. A February incident similarly exposed over 18,000 user records through AI-generated code flaws, highlighting systemic security debt across the vibe-coding ecosystem.
No Comment! Be the first one.