Session-token disclosure via missing anti-caching headers
Published Nov 21, 2025 · Updated Nov 21, 2025
Sensitive-data caching in WorkOS AuthKit Next.js before 2.11.1 allows remote attackers to obtain another user's session token. Authenticated response paths omit defensive Cache-Control and Vary headers, allowing a configured CDN to reuse one user's token-bearing response for another user. Exposure requires CDN caching on authenticated routes; Vercel deployments are unaffected unless those routes manually enable caching.
Summary
What happened
Sensitive-data caching in WorkOS AuthKit Next.js before 2.11.1 allows remote attackers to obtain another user's session token. Authenticated response paths omit defensive Cache-Control and Vary headers, allowing a configured CDN to reuse one user's token-bearing response for another user. Exposure requires CDN caching on authenticated routes; Vercel deployments are unaffected unless those routes manually enable caching.
The record
- CVE
- CVE-2025-64762
- Published
- Nov 21, 2025
- Updated
- Nov 21, 2025
- Vendor
- WorkOS
- Product
- AuthKit Next.js
- Classifications
- CWE-524, CAPEC-204, T1539
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 21, 2025CVE publishedPublication date reported by the CVE source.
- Nov 21, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.11.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo