151 wires and counting

$ follow Supabase

Keep up with Supabase in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-08-18
stories 85

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

SUPABASE HARDENS CORS AND SHIPS PROMPT-INJECTION EVALS

By RepoJournal · Filed · About Supabase · Composed from the cited sources · methodology

A config hardening for self-hosted envoy plus four new security evals signal Supabase is closing attack surfaces on both the infrastructure and AI agent fronts.

Supabase shipped a CORS hardening for self-hosted deployments, restricting access to `/pg` routes to the studio dashboard instead of the permissive global mode [1]. Meanwhile, four new regression evals, mirroring the AgentDojo benchmark, now test agent robustness against prompt injection through the MCP server's free-text tools like `execute_sql` and `query_logs` [2]. These evals reflect a growing focus on AI security, especially as MCP debugging tools and the Supabase agent skill are now documented [3]. On the CLI side, a migration ordering fix addresses inconsistent behavior across `db pull`, `migration list`, and shadow db replays, which could cause false conflicts and reversed migrations [4]. Storage v1.70.0 and postgres 17.6.1.163 released as portable, smoke-tested runtime artifacts, keeping the local stack current [5][6].

Action items

References

  1. [1] chore: update cors for pg routes (#49136) ↗ supabase/supabase
  2. [2] feat(evals): prompt-injection security scenarios (AgentDojo-style) (#202) ↗ supabase/evals
  3. [3] docs: mention MCP debugging tools and Supabase agent skill in debugging docs (#48978) supabase/supabase ↗
  4. [4] fix(cli): order migrations consistently ↗ supabase/cli
  5. [5] storage v1.70.0 ↗ supabase/slim-services
  6. [6] postgres 17.6.1.163 ↗ supabase/slim-services

Quick answers

What shipped in Supabase on August 18, 2026?
A config hardening for self-hosted envoy plus four new security evals signal Supabase is closing attack surfaces on both the infrastructure and AI agent fronts. In total, 38 commits, 40 pull requests, and 7 releases landed.
Who contributed to Supabase on August 18, 2026?
13 developers shipped this update, including Miranda Limonczenko, Etienne Stalmans, Jordi Enric, dnywh, dependabot, jgoux, supabase-cli-releaser, and 7ttp, and 5 more.
What were the notable Supabase updates?
chore: update cors for pg routes (#49136), feat(evals): prompt-injection security scenarios (AgentDojo-style) (#202), and docs: mention MCP debugging tools and Supabase agent skill in debugging docs (#48978).