CVE-2025-64762
Workos Authkit-Nextjs ≤ 2.11.1
Raw vector
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:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2025-64762 is a high-severity Use of Cache Containing Sensitive Information (CWE-524) vulnerability in Workos Authkit-Nextjs. Its CVSS base score is 8.0 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Unsecured Credentials (T1552); ranked at the 31th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SC-4 (Information in Shared System Resources) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-64762 affects the AuthKit library for Next.js, which provides authentication and session management helpers using WorkOS and AuthKit. In versions 2.11.0 and prior, authenticated responses lack defensive anti-caching headers, enabling session tokens to be cached and served to unintended users in environments with CDN caching enabled. This vulnerability, associated with CWE-524 (use of cache fields with cookie data), carries a CVSS v3.1 base score of 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N), indicating critical severity due to high impacts on confidentiality and integrity.
Remote unauthenticated attackers can exploit this issue in deployments where CDN caching is active on authenticated paths, such as custom configurations beyond default Next.js on Vercel setups. By accessing cached responses, attackers receive session tokens from other users, potentially enabling session hijacking, account takeover, or unauthorized access to protected resources without direct interaction with the target application.
The vulnerability is patched in authkit-nextjs version 2.11.1, which adds anti-caching headers to all responses behind authentication. Developers should upgrade immediately and review caching configurations, particularly for CDNs. Official advisories, including the GitHub security advisory GHSA-p8pf-44ff-93gf, release notes for v2.11.1, and the patching commit 94cf438124993abb0e7c19dac64c3cb5724a15ea, provide full details on the fix. Next.js applications on Vercel remain unaffected unless caching is manually enabled on authenticated routes.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-198354
Vulnerability Data
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,…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V14.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces access authorizations so that cached sensitive data cannot be read by actors outside the intended sphere.
Directly prevents unauthorized transfer of information through shared resources such as caches.
Controls information flows to keep sensitive data from leaving its authorized control sphere via caches.
Requires cryptographic or other protection of sensitive information at rest, which covers cached data.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Protecting confidentiality of data-at-rest covers caches that persist sensitive information.
Enforcing least-privilege access permissions directly limits who can read cached sensitive data.
Protecting data-in-use can mitigate exposure when caches hold transient sensitive values.
Logical access controls on environments reduce the chance an outsider can reach the cache.
Hardened configuration baselines can disable or secure caching of sensitive data.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Data leakage prevention can block unauthorized access to cached sensitive information.
Information access restriction directly limits who can read cached sensitive data.
Information deletion ensures sensitive data is removed from caches when no longer needed.
Cryptography can protect cached data at rest, but does not address access control scope.
Secure coding practices prevent caching of sensitive data outside intended boundaries.
Environment separation reduces risk of cache exposure across development/test/production.