Supabase APIDeprecationmedium

Supabase drops CBC TLS 1.2 ciphers on project APIs on Nov 10, 2026

Detected
Oct 13, 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 (TLS_ECDHE_*_WITH_AES_*_CBC_SHA*) on project HTTP APIs starting November 10, 2026. This affects Auth, Data API, Storage, Realtime, and Edge Functions endpoints; fewer than 0.0001% of connections currently use these ciphers.

What to do

Audit any clients connecting over HTTPS on end-of-life OSes or embedded devices. Ensure they support at least one GCM or ChaCha20-Poly1305 TLS 1.2 cipher or TLS 1.3. Update the OS/TLS library if needed.

Affected

endpoint: <ref>.supabase.co HTTP API (Auth, Data API, Storage, Realtime, 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_SHA384

Source: supabase.com (Supabase's own page, checked by Breakwatch)

Is your code affected?

Search your repositories for the Supabase SDK and the names above:

npm: @supabase/supabase-jspip: supabaseruby: supabasego: github.com/supabase-community/supabase-gorust: postgrest

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

Get Supabase API changes by email

Once a week: the breaking changes and upcoming deadlines for Supabase, each linked to the vendor's own page. Free, no account. One-click unsubscribe.

More Supabase API changes

Every Supabase API change →