CVE-2025-64762
Unknown Unknown - Not Provided

BaseFortify

Vulnerability report for CVE-2025-64762, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2025-11-21

Last updated on: 2025-12-11

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2025-11-21
Last Modified
2025-12-11
Generated
2026-07-06
AI Q&A
2025-11-21
EPSS Evaluated
2026-07-05
NVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
workos authkit-nextjs to 2.11.1 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-524 The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability exists in the AuthKit library for Next.js versions 2.11.0 and below, where authenticated responses do not include anti-caching headers. As a result, in environments using CDN caching, session tokens may be cached and served to multiple users, potentially exposing sensitive authentication information. The issue is fixed in version 2.11.1 by applying anti-caching headers to all authenticated responses.

Impact Analysis

If you use AuthKit for Next.js version 2.11.0 or below and have CDN caching enabled on authenticated paths, session tokens could be cached and inadvertently shared with other users. This can lead to unauthorized access to user sessions and compromise account security.

Mitigation Strategies

Upgrade authkit-nextjs to version 2.11.1 or later, which applies anti-caching headers to all responses behind authentication to prevent session tokens from being cached and served to multiple users. Additionally, review your CDN caching configuration to ensure that authenticated paths do not have cache headers enabled.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-64762. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart