Lovable has a mass data breach affecting every project created before november 2025.
I made a lovable account today and was able to access another users source code, database credentials, AI chat histories, and customer data are all readable by any free account.
nvidia, microsoft, uber, and spotify employees all have accounts. the bug was reported 48 days ago. its not fixed. They marked it as duplicate and left it open.
Heres how i accessed another user's profile, listed their public projects, and downloaded the source code of an admin panel for Connected Women in AI, a real danish nonprofit. the project was last edited 10 days ago. the developer has 3,703 edits this year. this is not abandoned. this is active.
i extracted the database credentials from the source code and queried it. got back real names, real companies, real linkedin profiles. speakers from Accenture Denmark and Copenhagen Business School. not test data. not "John Doe". real people at real companies who have no idea their information is exposed.
this is not hacking. this is five API calls from a free account.
lovable patched this for new projects. they never patched it for existing ones.
i tested both today. a project created in april 2026 returns 403 forbidden. the same developer's older project, actively edited 10 days ago, returns 200 OK with the full source tree. same API. same endpoint. same free account. same session. one is protected. the other is wide open.
the first hackerone report was filed march 3 2026. lovable marked it triaged. then they shipped ownership checks for new projects and left every existing project exposed. 48 days later nothing has changed.
they chose to protect new users and abandon everyone who already built on the platform.
it gets worse. every conversation you have with lovable's AI is stored and readable through the same bug.
i read the full chat history of a project built for a real danish nonprofit. the developer discussed database schemas with the AI. tables with email, first_name, last_name, date_of_birth, company, job_title, linkedin_url, stripe_customer_id. the AI generated SQL migrations. supabase credentials appeared in the conversation. all of it is readable by any free account.
people tell the AI what they want to build. they paste error logs. they discuss their business logic. they share credentials. lovable stores all of it and exposes all of it.
Another awful business decision made by SF elites.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
AMD is shipping a vulnerable kernel driver in the Razer Blade 16 BIOS updater. its sitting in the same folder as ANOTHER vulnerable driver that's been publicly known and documented as dangerous for years
both are signed. both can be weaponized by malware to bypass your antivirus, take complete control of your computer from the inside, read anything stored in memory including passwords and crypto wallet keys, and load ransomware /Malware without your PC putting up a fight
this is exactly what ransomware / malware operators and state backed groups hunt for every single day
BiosToolCommonDriver.sys, internal name `affdriver` AMD Field Fusing / RPMC. 47KB. WHQL + AMD Sectigo dual signed, signed october 2023. AMD's cert has since expired but the timestamp keeps the sig valid, still loads on current Windows
18 IOCTLs, all ghidra confirmed, all verified with a working PoC
any admin level process opening this device can read or write any physical memory address up to 4KB per call, read or write any PCI device's config space, read or write any CPU MSR with no allowlist (one write to IA32_LSTAR redirects every syscall on the system through attacker code), do raw port I/O across the full 64K range including keystroke injection via the i8042 keyboard controller, read BIOS flash contents directly, allocate contiguous DMA buffers, and translate any virtual address to physical which breaks KASLR
admin only device ACL is meaningless in BYOVD because attackers already have admin when they load the driver. not on microsofts HVCI blocklist. no CVE. densest primitive set ive seen in a single WHQL signed driver
okay why should you care about some obscure AMD driver if youre not a reverse engineer
malware on your machine still has to beat your AV and EDR before it can do real damage. vulnerable signed kernel drivers like this one are exactly how ransomware operators kill your protection from ring 0 before they encrypt anything
every driver we burn is one less weapon in the ransomware toolkit. thats why this matters