What’s Vulnerable › Vulnerabilities
CVE-2025-64762: authkit-nextjs may let session cookies be cached in CDNs
- Severity: critical (CVSS 9.1 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.4% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2025-11-21 · updated 2026-10-07
- Weakness: CWE-524
Description
The AuthKit library for Next.js provides convenient helpers for authentication and session management using WorkOS & AuthKit with Next.js. 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.js applications deployed on Vercel are unaffected unless they manually enable CDN caching by setting cache headers on authenticated paths. Patched in authkit-nextjs 2.11.1, which applies anti-caching headers to all responses behind authentication.
Affected products
- workos authkit-nextjs: before 2.11.1 — fixed in 2.11.1
How to fix
Upgrade to a fixed version: workos authkit-nextjs 2.11.1. Check the vendor advisory for mitigations.
References
- https://github.com/workos/authkit-nextjs/commit/94cf438124993abb0e7c19dac64c3cb5724a15ea
- https://github.com/workos/authkit-nextjs/releases/tag/v2.11.1
- https://github.com/workos/authkit-nextjs/security/advisories/GHSA-p8pf-44ff-93gf
Get alerted when CVE-2025-64762 or the next vulnerability affects your stack