How severe is GHSA-2mqv-4j3r-vjvp?

GHSA-2mqv-4j3r-vjvp has a CVSS score of 6.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-2mqv-4j3r-vjvp?

GHSA-2mqv-4j3r-vjvp affects the following packages: @auth0/nextjs-auth0 (npm). Ecosystems affected: npm.

How do I fix GHSA-2mqv-4j3r-vjvp?

Update @auth0/nextjs-auth0 to 1.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2mqv-4j3r-vjvp is resolved across your whole dependency graph.

How do I detect GHSA-2mqv-4j3r-vjvp in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @auth0/nextjs-auth0. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-2mqv-4j3r-vjvp 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-2mqv-4j3r-vjvp?

O3 pinpoints whether GHSA-2mqv-4j3r-vjvp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-2mqv-4j3r-vjvp actively exploited in the wild?

No public exploit code has been indexed for GHSA-2mqv-4j3r-vjvp 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-2mqv-4j3r-vjvp?

GHSA-2mqv-4j3r-vjvp has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 47th 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.

What type of vulnerability is GHSA-2mqv-4j3r-vjvp?

GHSA-2mqv-4j3r-vjvp is classified as Open Redirect (CWE-601). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-2mqv-4j3r-vjvp published, and has it been updated?

GHSA-2mqv-4j3r-vjvp was published on December 16, 2021 and was last updated on March 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-2mqv-4j3r-vjvp: Open redirect in @auth0/nextjs-auth0 (Medi…

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk47th percentile+0.46%

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.

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

@auth0/nextjs-auth0npm

608Kdownloads / week

Description

Overview

Versions <=1.6.1 do not filter out certain returnTo parameter values from the login url, which expose the application to an open redirect vulnerability.

Am I affected?

You are affected by this vulnerability if you are using @auth0/nextjs-auth0 version <=1.6.1.

How to fix that?

Upgrade to version >=1.6.2

Will this update impact my users?

The fix provided in the patch will not affect your users.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@auth0/nextjs-auth0`	all versions	1.6.2

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @auth0/nextjs-auth0 to 1.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2mqv-4j3r-vjvp 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 pinpoints whether GHSA-2mqv-4j3r-vjvp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-2mqv-4j3r-vjvp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Overview Versions `<=1.6.1` do not filter out certain `returnTo` parameter values from the login url, which expose the application to an open redirect vulnerability. ### Am I affected? You are affected by this vulnerability if you are using `@auth0/nextjs-auth0` version `<=1.6.1`. ### How to fix that? Upgrade to version `>=1.6.2` ### Will this update impact my users? The fix provided in the patch will not affect your users.

O3 Security · Impact-Aware SCA

Is GHSA-2mqv-4j3r-vjvp in your dependencies?

O3 detects GHSA-2mqv-4j3r-vjvp across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-2mqv-4j3r-vjvp