Session persistence via missing JWE expiration claim
Published Apr 29, 2025 · Updated Apr 30, 2025
Insufficient session expiration in Auth0 Next.js SDK 4.0.1 through 4.5.0 allows remote authenticated users to retain valid sessions. The session-cookie encryption path in src/server/cookies.ts creates an EncryptJWT without calling setExpirationTime, so the JWE has no internal exp claim. A user who retains the encrypted session token can reuse it after the browser cookie expires or is cleared, preserving only the access already granted by that session.
Summary
What happened
Insufficient session expiration in Auth0 Next.js SDK 4.0.1 through 4.5.0 allows remote authenticated users to retain valid sessions. The session-cookie encryption path in src/server/cookies.ts creates an EncryptJWT without calling setExpirationTime, so the JWE has no internal exp claim. A user who retains the encrypted session token can reuse it after the browser cookie expires or is cleared, preserving only the access already granted by that session.
The record
- CVE
- CVE-2025-46344
- Published
- Apr 29, 2025
- Updated
- Apr 30, 2025
- Vendor
- Auth0
- Product
- Auth0 Next.js SDK
- Classifications
- CWE-613, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 29, 2025CVE publishedPublication date reported by the CVE source.
- Apr 30, 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=>= 4.0.1, < 4.5.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.
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