NVD
Briefly

"Prior to version 3.20.0, using RpcServer.toWebHandler or HttpApp.toWebHandlerRuntime in a Next.js App Router could lead to race conditions, allowing concurrent requests to read incorrect context."
"Under production traffic, auth() from @clerk/nextjs/server could return a different user's session due to improper synchronization of shared resources."
"Version 3.20.0 contains a fix for the issue, ensuring that Node.js AsyncLocalStorage-dependent APIs function correctly within Effect fibers."
Effect is a TypeScript framework that includes multiple packages for building applications. Prior to version 3.20.0, using RpcServer.toWebHandler or HttpApp.toWebHandlerRuntime in a Next.js App Router could lead to race conditions. This allowed concurrent requests to read incorrect context, resulting in issues like auth() returning a different user's session. The release of version 3.20.0 addresses this critical issue, ensuring proper synchronization and context management under production traffic.
Read at Nist
Unable to calculate read time
[
|
]