cve.bz

CVE-2025-46344 auth0 nextjs-auth0: Insufficient Session Expiration

4.9 mediumEPSS 0.4%Fix available

Medium (4.9) in auth0 nextjs-auth0. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in @auth0/nextjs-auth0 4.5.1.

On this page
The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. Versions starting from 4.0.1 and prior to 4.5.1, do not invoke `.setExpirationTime` when generating a JWE token for the session. As a result, the JWE does not contain an internal expiration claim. While the session cookie may expire or be cleared, the JWE remains valid. This issue has been patched in version 4.5.1.

Severity

CVSS 4.0

4.9 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U
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; 40th 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-04-30. 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-613 Insufficient Session Expiration deprecated by MITRE see CWE-1463, CWE-1464
OWASP Top 10
A07:2025 Authentication Failures
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.5.1

Ask an AI about this CVE

Show the promptExplain CVE-2025-46344 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-46344?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-46344?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-46344 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.5.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-pjr6-jx7r-j4r6npm@auth0/nextjs-auth0>=4.0.1 <4.5.14.5.1

References

Check your stackJSON