Description
In authkit-nextjs version 2.11.0 and below, authenticated responses do not defensively apply anti-caching headers. In environments where CDN caching is enabled, this can result in session tokens being included in cached responses and subsequently served to multiple users.
Next.
Recommendation
Update the @workos-inc/authkit-nextjs package to the latest compatible version. Followings are version details:
- Affected version(s): <= 2.11.0
- Patched version(s): 2.11.1
References
Could your website be exposed too?
SmartScanner can check your website for authkit-nextjs may let session cookies be cached in CDNs and gives you actionable findings to investigate.
Start a free scanRelated Issues
- @workos-inc/authkit-nextjs session replay vulnerability - CVE-2024-29901
- Turbo Frame responses can restore stale session cookies - CVE-2025-66803
- @workos-inc/authkit-nextjs refresh tokens are logged when the debug flag is enabled - CVE-2024-51752
- content-security-policy-parser Prototype Pollution Vulnerability May Lead to RCE - CVE-2025-55164
You might also like:
See something that needs correcting? Let us knowUpdated November 21, 2025