Supabase APIBreaking changehigh
Supabase drops CBC TLS 1.2 cipher suites from its APIs on Nov 10, 2026
- Detected
- Oct 14, 2026
- Effective
- Nov 10, 2026(took effect 6 days ago)
- Confidence
- 97%
What changed
Supabase will remove four CBC-mode TLS 1.2 cipher suites (TLS_ECDHE_*_WITH_AES_*_CBC_SHA*) from all project HTTP APIs (Auth, Data API, Storage, Realtime, Edge Functions) starting November 10, 2026. Clients using only these deprecated ciphers will lose connectivity.
What to do
Verify that all clients connecting to Supabase over HTTPS support at least one GCM or ChaCha20-Poly1305 TLS 1.2 cipher or TLS 1.3. Update end-of-life OS or TLS libraries accordingly before November 10, 2026.
Affected
endpoint: *.supabase.co (Auth)endpoint: *.supabase.co (Data API)endpoint: *.supabase.co (Storage)endpoint: *.supabase.co (Realtime)endpoint: *.supabase.co (Edge Functions)header: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256header: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256header: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384header: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384Source: supabase.com (Supabase's own page, checked by Breakwatch)
Is your code affected?
Search your repositories for the Supabase SDK and the names above:
Or let Breakwatch do it: connect a repo and see which files call Supabase, then get the next change as an alert pointing at those files. Check a repo free