How severe is GHSA-pjr6-jx7r-j4r6?

No CVSS score has been assigned to GHSA-pjr6-jx7r-j4r6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-pjr6-jx7r-j4r6?

GHSA-pjr6-jx7r-j4r6 affects the following packages: @auth0/nextjs-auth0 (npm). Ecosystems affected: npm.

How do I fix GHSA-pjr6-jx7r-j4r6?

Update @auth0/nextjs-auth0 to 4.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pjr6-jx7r-j4r6 is resolved across your whole dependency graph.

How do I detect GHSA-pjr6-jx7r-j4r6 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @auth0/nextjs-auth0, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-pjr6-jx7r-j4r6 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-pjr6-jx7r-j4r6?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pjr6-jx7r-j4r6 can be triaged on real exposure rather than presence alone.

Is GHSA-pjr6-jx7r-j4r6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-pjr6-jx7r-j4r6 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-pjr6-jx7r-j4r6?

GHSA-pjr6-jx7r-j4r6 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 33th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-pjr6-jx7r-j4r6 published, and has it been updated?

GHSA-pjr6-jx7r-j4r6 was published on April 29, 2025 and was last updated on April 30, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-pjr6-jx7r-j4r6 — @auth0/nextjs-auth0

Fix: auth0/nextjs-auth0@a4f061a

GHSA-pjr6-jx7r-j4r6 is a security vulnerability in @auth0/nextjs-auth0. A fix is available for @auth0/nextjs-auth0 — see the affected versions and patch details below.

Auth0 NextJS SDK v4 Missing Session Invalidation

Also known asCVE-2025-46344

Published

Apr 29, 2025

Updated

Apr 30, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 24, 2026 · OSV.dev, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-pjr6-jx7r-j4r6.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs33th percentile — riskier than 33% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

41other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@auth0/nextjs-auth0npm

583Kdownloads / week

Description

Overview

Auth0 NextJS v4.0.1 to v4.5.0 does 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.

Am I Affected?

You are affected if you are using Auth0 NextJS SDK v4.

Fix

Upgrade to v4.5.1.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@auth0/nextjs-auth0`	≥ 4.0.1&&< 4.5.1	4.5.1`npm install @auth0/nextjs-auth0@4.5.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @auth0/nextjs-auth0, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @auth0/nextjs-auth0 to 4.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pjr6-jx7r-j4r6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pjr6-jx7r-j4r6 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-pjr6-jx7r-j4r6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Overview Auth0 NextJS `v4.0.1` to `v4.5.0` does 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. ### Am I Affected? You are affected if you are using Auth0 NextJS SDK v4. ### Fix Upgrade to `v4.5.1`.

O3 Security · Impact-Aware SCA

Is GHSA-pjr6-jx7r-j4r6 in your dependencies?

O3 Security finds GHSA-pjr6-jx7r-j4r6 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works