Skip to content

Supabase's October 30 change: new public tables need a grant for Data API access. What to doSupabase's October 30 change is live: new public tables need a grant for Data API access. What broke and how to fix it

24 tools · 139 fixes · 42 issue guides · Sources: Supabase, GitHub, postgresql.org, Vercel + 53

Incident feed

Vercel says compromised eMudhra certificate authority keys still put Node.js 20 and runtimes you install yourself at risk

On October 27, 2026, Vercel published a security bulletin about eight eMudhra intermediate certificate authorities whose private keys could be recovered, which would let anyone holding them issue a trusted certificate for any website. Vercel says most projects need no action and it has removed trust in the affected roots as updated runtimes became available, but the rollout to managed Node.js runtimes for Functions is still in progress. Projects still on Node.js 20.x must move to 22 or newer and redeploy, and runtimes or certificate packages you install yourself need updating.

Share link · Share on X

Information disclosureVercel

What was reported

Vercel's security bulletin, dated October 27, 2026, says that on October 17 researchers found the private keys for eight intermediate certificate authorities operated by eMudhra (emSign) could be recovered. Anyone holding those keys could issue a trusted certificate for any website. eMudhra revoked the intermediates on October 18, and Vercel says the major browsers and operating systems blocked them within days. The bulletin warns that revocation alone does not protect most non-browser clients, because they never check revocation status. Node.js, Python's certifi package, Go and most container images each carry their own list of trusted roots, and each list stays exposed until it is updated.

Vercel says most projects need no action. It updated builds, Vercel Functions, Sandbox images and Image Optimization, and projects on Node.js 22 or newer receive the update without a redeploy. Vercel says it is still rolling the change across its managed Node.js runtimes for Functions. Projects still on Node.js 20.x must change to 22 or newer and redeploy, because Node.js 20 is end of life and will not receive an updated certificate list. Vercel does not manage runtimes and packages you install or pin yourself, including Node.js or Python installed inside a Sandbox or custom base image, container images you build, and pinned certifi packages. Update these to releases that drop the affected roots, or rebuild on an updated base image. The roots to look for are AAA Certificate Services, emSign Root TLS CA - G3 and emSign ECC Root CA - G3.

Outside Vercel, the bulletin lists external backends, CI runners and developer machines. It says Node.js 22.23.4, 24.22.1 and 26.12.1, certifi 2026.10.19 and Homebrew's current ca-certificates package drop the affected roots. The Node.js October 21, 2026 security release lists the certificate update as "ca-cert (eMudhra Intermediate CA Compromise)" for 26.x, 24.x and 22.x. Vercel says a client is exposed when it still trusts the eMudhra roots and connects over a network an attacker can intercept, such as public Wi-Fi or hijacked DNS, and that inbound traffic to your site is not affected. Vercel advises avoiding untrusted networks on machines that have not been updated.

How to prevent it

Update the runtimes and certificate stores you manage so they no longer trust the affected roots. On Vercel, that includes moving Node.js 20.x projects to 22 or newer and redeploying.

Sources

Related

The weekly fix

The weekly fix: 3 real security mistakes in vibe-coded apps and how to fix them, every Tuesday.

One email, every Tuesday. A welcome note follows the first signup.