VulnerabilityPublished 21 Nov 2025Updated 24 Nov 2025

CVE-2025-64762: workos authkit-nextjs · Use of Cache Containing Sensitive Information

Affects workos authkit-nextjsSource CVE Database V5

Compare

Not known to be exploited · CVSS 8.0 High : upgrade to 2.11.1 soon.

Data as of 29 Oct 2026, 14:41 UTC

CVSS 4.0 base score

8.0High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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:U

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: High
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: Unreported

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the vulnerable system. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the vulnerable system.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: Unreported: Based on threat intelligence sources each of the following must apply: · No knowledge of publicly available proof-of-concept · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation 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 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade workos authkit-nextjs to 2.11.1.

Affected software

Product	Affected	Fixed in
npmauthkit-nextjs`pkg:npm/authkit-nextjs`Other threats	Affected <2.11.1	Fixed in 2.11.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade authkit-nextjs to version 2.11.1 or later to ensure anti-caching headers are applied to all authenticated responses. Review and audit CDN configurations to confirm that caching is disabled on any endpoints handling authentication or session tokens. Implement strict cache-control headers such as 'Cache-Control: no-store, no-cache, must-revalidate, proxy-revalidate' and 'Pragma: no-cache' on all sensitive routes. Conduct penetration testing and code reviews to verify that no other endpoints inadvertently expose sensitive data via caching. For organizations using custom or third-party CDNs, enforce policies that prevent caching of authenticated content. Additionally, monitor access logs and CDN cache hit/miss ratios for anomalies that could indicate token leakage. Educate development teams on secure caching practices and the risks of caching sensitive information. Finally, consider implementing short-lived session tokens and multi-factor authentication to reduce the impact of any potential token exposure.

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.

Impact

For European organizations, this vulnerability can lead to severe data breaches involving session tokens, enabling attackers to impersonate legitimate users and access sensitive resources. This compromises user confidentiality and integrity, potentially exposing personal data protected under GDPR. Organizations relying on authkit-nextjs for authentication in customer-facing or internal applications that use CDN caching are particularly at risk. The exposure of session tokens can facilitate lateral movement within networks, privilege escalation, and unauthorized data access. The impact extends to reputational damage, regulatory penalties, and operational disruptions. Given the widespread adoption of Next.js and WorkOS in Europe’s tech ecosystem, especially among SaaS providers and enterprises leveraging modern web frameworks, the threat is significant. The risk is heightened in sectors with stringent compliance requirements such as finance, healthcare, and government services. Additionally, organizations using custom CDN configurations or self-hosted CDN solutions are more vulnerable compared to those on managed platforms like Vercel that do not enable caching on authenticated routes by default.

Summary

The vulnerability identified as CVE-2025-64762 affects authkit-nextjs, a library facilitating authentication and session management in Next.js applications integrated with WorkOS. Versions prior to 2.11.1 fail to apply anti-caching HTTP headers on authenticated responses. In environments where CDN caching is enabled, this oversight allows session tokens and other sensitive authentication data to be cached by intermediary CDN nodes. Consequently, these cached responses can be served to other users, leading to session token leakage and unauthorized access. The vulnerability is categorized under CWE-524, which concerns the use of caches containing sensitive information. The issue does not require authentication or user interaction to exploit and can be triggered remotely over the network. The CVSS 4.0 base score is 8.0, reflecting high severity due to the ease of exploitation and the critical impact on confidentiality and integrity. Notably, Next.js applications deployed on Vercel are not vulnerable by default, as Vercel does not enable CDN caching on authenticated paths unless explicitly configured. The fix introduced in authkit-nextjs version 2.11.1 adds appropriate anti-caching headers to all authenticated responses, preventing sensitive data from being cached and served to unauthorized parties. While no active exploits have been reported, the vulnerability poses a significant risk in any deployment scenario where CDN caching is enabled on authenticated endpoints.

CWE-524Use of Cache Containing Sensitive Information (opens in a new tab)
Base weakness
The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere.
Architecture and Design
Protect information stored in cache.
Architecture and Design
Do not store unnecessarily sensitive information in the cache.
Architecture and Design
Consider using encryption in the cache.
OWASP ASVS 4.0.3
V8.1.1 (opens in a new tab)
V8.1.2 (opens in a new tab)
Attack patterns
Lifting Sensitive Data Embedded in Cache (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Nov 2025, 04:42 UTC

WeaknessesCWE-524

Technical details

References

Community reviews

Related threats