by Kastro
Paper/Archive/CVE-2025-64762

CVE-2025-64762

workos authkit-nextjs — authkit-nextjs may let session cookies be cached in CDNs

EPSS 0.4%CVSS 9.1
critical.is priorityof 100
34
CVSS 9.1 (NVD)9.1 / 10 × 3027.3Not in CISA KEV+300.0EPSS percentile 33.4.334 × 206.7No public exploit+100.0SSVC exploitation: none+100.0
Description · from the CVE record

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

ProductAffectedFixed inSource
authkit-nextjs< 2.11.1–CNA

Scores by source

NVD9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
GitHub_M (CNA)8.0CVSS: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:U
CISA ADPSSVCExploitation: none · Automatable: yes · Technical impact: total

References

refgithub.com/workos/authkit-nextjs/security/advisories/GHSA-p8pf-44ff-93gfrefgithub.com/workos/authkit-nextjs/commit/94cf438124993abb0e7c19dac64c3cb5724a15earefgithub.com/workos/authkit-nextjs/releases/tag/v2.11.1