CVE-2025-64762 Vulnerability Analysis & Exploit Details

CVE-2025-64762
Vulnerability Scoring

9.1
/10
Critical Risk

As a catastrophic security flaw, CVE-2025-64762 has severe implications, demanding immediate intervention.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2025-64762 Details

Status: Analyzed

Last updated: 🕠 11 Dec 2025, 17:45 UTC
Originally published on: 🕑 21 Nov 2025, 02:15 UTC

Time between publication and last update: 20 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

CVE-2025-64762 Vulnerability Summary

CVE-2025-64762: 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.

Assessing the Risk of CVE-2025-64762

Access Complexity Graph

The exploitability of CVE-2025-64762 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2025-64762

With low attack complexity and no required privileges, CVE-2025-64762 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2025-64762, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2025-64762, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2025-64762 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2025-64762 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: None
    CVE-2025-64762 does not impact system availability.

CVE-2025-64762 References

External References

CWE Common Weakness Enumeration

CWE-524

CAPEC Common Attack Pattern Enumeration and Classification

  • Lifting Sensitive Data Embedded in Cache CAPEC-204 An adversary examines a target application's cache, or a browser cache, for sensitive information. Many applications that communicate with remote entities or which perform intensive calculations utilize caches to improve efficiency. However, if the application computes or receives sensitive information and the cache is not appropriately protected, an attacker can browse the cache and retrieve this information. This can result in the disclosure of sensitive information.

Vulnerable Configurations

  • cpe:2.3:a:workos:authkit-nextjs:0.1.0:-:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.1.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.1.0:rc0:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.1.0:rc0:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.1.0:rc1:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.1.0:rc1:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.1.0:rc2:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.1.0:rc2:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.1.0:rc3:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.1.0:rc3:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.3.0:-:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.3.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.3.0:rc0:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.3.0:rc0:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.4.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.4.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.4.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.4.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.4.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.4.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.5.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.5.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.5.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.5.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.5.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.5.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.5.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.5.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.6.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.6.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.6.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.6.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.6.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.6.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.7.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.7.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.8.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.8.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.8.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.8.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.8.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.8.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.9.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.9.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.10.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.10.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.10.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.10.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.11.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.11.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.11.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.11.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.11.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.11.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.12.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.12.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.12.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.12.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.12.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.12.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.12.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.12.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.13.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.13.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.13.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.13.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.13.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.13.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.14.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.14.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.15.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.15.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.16.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.16.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.16.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.16.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.16.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.16.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.17.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.17.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.17.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.17.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:0.17.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:0.17.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:1.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:1.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:1.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:1.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:1.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:1.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:1.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:1.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:1.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:1.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:1.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:1.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:1.4.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:1.4.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:1.4.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:1.4.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.2.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.2.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.2.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.2.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.2.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.3.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.3.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.3.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.3.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.3.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.3.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.4.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.4.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.4.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.4.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.4.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.4.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.4.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.4.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.4.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.4.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.4.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.4.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.4.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.4.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.5.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.5.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.6.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.6.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.7.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.7.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.7.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.7.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.8.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.8.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.9.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.9.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.10.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.10.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:workos:authkit-nextjs:2.11.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:workos:authkit-nextjs:2.11.0:*:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2025-64762: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-52691 – Successful exploitation of the vulnerability could allow an unauthenticated attacker to upload arbitrary files to any location on the mail server, ...
  • CVE-2025-15168 – A vulnerability was identified in itsourcecode Student Management System 1.0. Affected is an unknown function of the file /statistical.php. Such ma...
  • CVE-2025-15167 – A vulnerability was determined in itsourcecode Online Cake Ordering System 1.0. This impacts an unknown function of the file /detailtransac.php. Th...
  • CVE-2025-15166 – A vulnerability was found in itsourcecode Online Cake Ordering System 1.0. This affects an unknown function of the file /updatesupplier.php?action=...
  • CVE-2025-15165 – A vulnerability has been found in itsourcecode Online Cake Ordering System 1.0. The impacted element is an unknown function of the file /updatecust...