{"answers":{"affected":"2 open source packages ship an affected version, including @workos-inc/authkit-nextjs. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-64762 in the wild and no public exploit code.","fix":"Upgrade @workos-inc/authkit-nextjs to 2.11.1 or later.","what":"CVE-2025-64762 is a high-severity vulnerability in workos authkit-nextjs, published on 21 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-64762 and fix it if it is affected.\n\nWhat it is: CVE-2025-64762 is a high-severity vulnerability in workos authkit-nextjs, published on 21 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-64762 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @workos-inc/authkit-nextjs (npm): affected all versions; fixed in 2.11.1\n- @workos-inc/authkit-nextjs (npm): affected all versions; fixed in 2.11.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-64762/ (Markdown: https://insights.sbomify.com/CVE-2025-64762/index.md)","id":"CVE-2025-64762","markdown":"https://insights.sbomify.com/CVE-2025-64762/index.md","name":"CVE-2025-64762","record":{"aliases":["GHSA-p8pf-44ff-93gf"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Next.js authentication library","requires_auth":"none","summary":"Attackers can steal session tokens if CDN caching is enabled, as the library fails to set anti-caching headers on authenticated responses.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"authkit-nextjs","vendor":"workos"}],"cvss":{"score":8,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-524","name":"Use of Cache Containing Sensitive Information"}],"description":"The AuthKit library for Next.js provides convenient helpers for authentication and session management using WorkOS \u0026 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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"authkit-nextjs may let session cookies be cached in CDNs","id":"CVE-2025-64762","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":2,"n_references":3,"next":{"headline":"Envoy forwards early CONNECT data in TCP proxy mode","id":"CVE-2025-64763"},"packages":[{"ecosystem":"npm","fixed":["2.11.1"],"introduced":["0"],"last_affected":[],"package":"@workos-inc/authkit-nextjs","purl":null,"source":"GHSA-p8pf-44ff-93gf"},{"ecosystem":"npm","fixed":["2.11.1"],"introduced":["0"],"last_affected":[],"package":"@workos-inc/authkit-nextjs","purl":"pkg:npm/%40workos-inc/authkit-nextjs","source":"GHSA-p8pf-44ff-93gf"}],"prev":{"headline":"OpenBao Privileged Operator Identity Group Root Escalation","id":"CVE-2025-64761"},"products":["authkit-nextjs"],"published":"2025-11-21","related":[{"cvss_score":4.8,"headline":"@workos-inc/authkit-nextjs session replay vulnerability","id":"CVE-2024-29901","kev_date_added":null,"published":"2024-03-29"},{"cvss_score":2.1,"headline":"Refresh tokens are logged when the debug flag is enabled in @workos-inc/authkit-nextjs","id":"CVE-2024-51752","kev_date_added":null,"published":"2024-11-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-11-24","vendors":["workos"]},"summary":"Attackers can steal session tokens if CDN caching is enabled, as the library fails to set anti-caching headers on authenticated responses.","url":"https://insights.sbomify.com/CVE-2025-64762/"}