AI agents mark RLS 'done' with USING(true) policies that leave data wide open
Real_KingZeotic · reddit · 2026-09-23
A Reddit post highlights a common security blind spot in agent-built apps, especially on lovable/bolt/supabase stacks: verification only checks that a write landed, not that protection actually works.
Typical failure: an agent enables RLS on a table, writes, reads it back, sees it exists, and marks the task done—but the policy it generated is USING (true), so RLS is technically on yet every row is readable by anyone. The same happens with 'private' storage buckets that remain world-readable and functions running with elevated access and no internal auth check. The author argues most verification pipelines stop one level too early and should verify what a permission actually does after the write.
More from coding & agent
- AI Agent Uncovers ~14-Year-Old Memory Leak in libuv's macOS fsevents Path — steipete · 2026-09-23
- Astra + Three.js Blocking + Midjourney + Seedance 2.5: A Multi-Angle AI Video Workflow — Ror_Fly · 2026-09-23
- The most exhausting AI loop: watching two agents fight over your PR — MikkoH · 2026-09-23
- Opus 5.5 one-shots an aesthetic 3D snake game, hailed as best design model yet — jiayuan_jy · 2026-09-23
- Design studio turns its website into an agentic harness that surfaces content via AI — LukeW · 2026-09-23
- Coinbase for Agents adds 6,000+ stocks, with x402 payments for live market data — kleffew94 · 2026-09-23