authkit-nextjs may let session cookies be cached in CDNs
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
@workos-inc/authkit-nextjsnpm | < 2.11.1 | 2.11.1 |
Affected products
2- workos/authkit-nextjsv5Range: < 2.11.1
Patches
Vulnerability mechanics
References
5- github.com/advisories/GHSA-p8pf-44ff-93gfghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2025-64762ghsaADVISORY
- github.com/workos/authkit-nextjs/commit/94cf438124993abb0e7c19dac64c3cb5724a15eaghsax_refsource_MISCWEB
- github.com/workos/authkit-nextjs/releases/tag/v2.11.1ghsax_refsource_MISCWEB
- github.com/workos/authkit-nextjs/security/advisories/GHSA-p8pf-44ff-93gfghsax_refsource_CONFIRMWEB
News mentions
0No linked articles in our index yet.