authkit-nextjs may let session cookies be cached in CDNs

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.0 · 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 · score source

EPSS

• CVE-2025-64762: 0.39% estimated exploitation activity in the next 30 days; percentile 33.52 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. Impact This vulnerability may lead to session caching, potentially allowing unauthorized users to obtain another user’s session token. The severity depends on deployment configuration, caching policy, and whether authenticated routes are inadvertently cached. Patches Patched in authkit-nextjs 2.11.1, which applies anti-caching headers to all responses behind authentication. Notes Authentication middleware should set anti-caching headers for authenticated routes as a defense in depth measure, but cannot guarantee these headers will not be overwritten elsewhere in the…

Published by the source

20 Nov 2025, 21:29 UTC

Last modified by the source

21 Nov 2025, 15:32 UTC

Source last checked

26 Oct 2026, 12:38 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-p8pf-44ff-93gf

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-p8pf-44ff-93gf

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-64762

Advisory: authkit-nextjs may let session cookies be cached in CDNs
IDs: CVE-2025-64762, GHSA-p8pf-44ff-93gf
Record: https://patchnext.com/advisories/cve-2025-64762 (revision 3, source checked 26 Oct 2026, 12:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @workos-inc/authkit-nextjs 2.11.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @workos-inc/authkit-nextjs: affected <= 2.11.0; fixed in 2.11.1

## Suggested inspection (read-only)
- `npm ls @workos-inc/authkit-nextjs --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @workos-inc/authkit-nextjs.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-p8pf-44ff-93gf (OSV record GHSA-p8pf-44ff-93gf lists affected ranges: npm @workos-inc/authkit-nextjs >=0 <2.11.1 (fixed))
- Verified: https://github.com/advisories/GHSA-p8pf-44ff-93gf (GitHub-reviewed advisory GHSA-p8pf-44ff-93gf lists affected ranges: npm @workos-inc/authkit-nextjs >=0 <=2.11.0)

Commands are suggestions: review each one before running it.