Supabase APIDeprecationmedium
Supabase drops CBC TLS 1.2 ciphers on project APIs from Nov 10, 2026
- Detected
- Oct 14, 2026
- Effective
- Nov 10, 2026(took effect 6 days ago)
- Confidence
- 95%
What changed
Supabase will disable four CBC-mode TLS 1.2 cipher suites (ECDHE-*-AES*-CBC-SHA*) on all project HTTP APIs (Auth, Data API, Storage, Realtime, Edge Functions) starting November 10, 2026 at the earliest. Clients on end-of-life operating systems or embedded devices that only support these legacy ciphers will lose connectivity.
What to do
Audit any HTTPS clients running on old OSes, legacy browsers, or embedded devices to ensure they support at least one GCM or ChaCha20-Poly1305 TLS 1.2 cipher or TLS 1.3. Update the OS or TLS library if needed.
Affected
endpoint: <ref>.supabase.co (Auth, Data API, Storage, Realtime, Edge Functions)header: TLS cipher: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256header: TLS cipher: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256header: TLS cipher: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384header: TLS cipher: 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