CVE-2025-64762: authkit-nextjs may let session cookies be cached in CDNs
Affects @workos-inc/authkit-nextjsSource GCVE Database
Not known to be exploited · CVSS 8.0 High : upgrade to 2.11.1 soon.
Data as of 13 Nov 2026, 18:48 UTC
- Patch
- Available – fixed in 2.11.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:UExploitation evidence
Disclosed: evidence found.
CVE published 21 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Upgrade @workos-inc/authkit-nextjs to 2.11.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@workos-inc/authkit-nextjs | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in authkit-nextjs version 2.11.1 that applies anti-caching headers to all authenticated responses. Users should upgrade to version 2.11.1 or later. Additionally, review application code, middleware, and infrastructure to ensure Cache-Control headers prevent caching of authenticated content. Avoid including sensitive or user-specific data in cacheable responses. For applications on Vercel, this issue does not apply unless CDN caching is manually enabled on authenticated paths.
Description
Authkit-nextjs versions 2.11.0 and below do not apply anti-caching headers on authenticated responses, which can cause session tokens to be cached by CDNs and served to unauthorized users. This issue is fixed in version 2.11.1 by adding anti-caching headers. The vulnerability primarily affects deployments that enable CDN caching on authenticated routes. Next.js apps on Vercel are not affected unless CDN caching is manually enabled on authenticated paths.
References
- github.com/workos/authkit-nextjs/security/advisories/GHSA-p8pf-44ff-93gf (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2025-64762 (opens in a new tab)
- github.com/workos/authkit-nextjs/commit/94cf438124993abb0e7c19dac64c3cb5724a15ea (opens in a new tab)
- github.com/workos/authkit-nextjs (opens in a new tab)
- github.com/workos/authkit-nextjs/releases/tag/v2.11.1 (opens in a new tab)