cve.bz

CVE-2025-48947 auth0 nextjs-auth0

7.7 highEPSS 0.4%Fix available

High (7.7) in auth0 nextjs-auth0. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in @auth0/nextjs-auth0 4.6.1.

On this page
The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. In Auth0 Next.js SDK versions 4.0.1 through 4.6.0, `__session` cookies set by auth0.middleware may be cached by CDNs due to missing Cache-Control headers. Three preconditions must be met in order for someone to be affected by the vulnerability: Applications using the NextJS-Auth0 SDK, versions between 4.0.1 to 4.6.0, applications using CDN or edge caching that caches responses with the Set-Cookie header, and if the Cache-Control header is not properly set for sensitive responses. Users should upgrade auth0/nextjs-auth0 to v4.6.1 to receive a patch.

Severity

CVSS 4.0

7.7 high
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 39th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-06-04. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-525 Use of Web Browser Cache Containing Sensitive Information
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • @auth0/nextjs-auth0 (npm): fixed in 4.6.1

Ask an AI about this CVE

Show the promptExplain CVE-2025-48947 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-48947?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-48947?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-48947 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
auth0 nextjs-auth0>= 4.0.1, < 4.6.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-f3fg-mf2q-fj3fnpm@auth0/nextjs-auth0>=4.0.1 <4.6.14.6.1

Attack patterns (CAPEC)

  • CAPEC-37 Retrieve Embedded Sensitive Data Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON