Next.js patches middleware bypass affecting custom auth setups
Next.js released a security advisory for a middleware-bypass technique that affects applications using middleware to enforce authentication. The bypass requires a specific header pattern that some CDN configurations strip; affected versions span 14.x and 15.x prior to this week's release.
If your middleware does auth (very common pattern in Next.js apps Brad and team have shipped), patch today. The CDN-strip behavior means that the bypass works only against a subset of deployments — but enumerating which ones takes longer than just patching.