How severe is GHSA-2j2x-hqr9-3h42?

No CVSS score has been assigned to GHSA-2j2x-hqr9-3h42 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2j2x-hqr9-3h42?

GHSA-2j2x-hqr9-3h42 affects the following packages: react-router (npm), react-router (npm). Ecosystems affected: npm.

How do I fix GHSA-2j2x-hqr9-3h42?

Update react-router to 7.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2j2x-hqr9-3h42 is resolved across your whole dependency graph.

How do I detect GHSA-2j2x-hqr9-3h42 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for react-router. 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-2j2x-hqr9-3h42 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-2j2x-hqr9-3h42?

O3 pinpoints whether GHSA-2j2x-hqr9-3h42 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-2j2x-hqr9-3h42 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2j2x-hqr9-3h42 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-2j2x-hqr9-3h42?

GHSA-2j2x-hqr9-3h42 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 6th 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-2j2x-hqr9-3h42?

GHSA-2j2x-hqr9-3h42 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-2j2x-hqr9-3h42 published, and has it been updated?

GHSA-2j2x-hqr9-3h42 was published on June 3, 2026 and was last updated on June 9, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-2j2x-hqr9-3h42

React Router's same-origin redirect with path starting // causes open redirect via protocol-relative URL reinterpretation

Also known asCVE-2026-40181

Published

Jun 3, 2026

Updated

Jun 9, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk6th percentile0.00%

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

2 pkgs affected

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

react-routernpm

46.7Mdownloads / week

Description

Certain URLs passed to the redirect function can trigger an open redirect to an external domain depending on the level of validation done by the application prior to returning the redirect.

[!NOTE] This does not impact your React Router application if you are using Declarative Mode (<BrowserRouter>)

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`react-router`	≥ 7.0.0&&< 7.14.1	7.14.1
📦npm	`react-router`	≥ 6.7.0&&< 6.30.4	6.30.4

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for react-router. 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 react-router to 7.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2j2x-hqr9-3h42 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-2j2x-hqr9-3h42 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-2j2x-hqr9-3h42. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Certain URLs passed to the `redirect` function can trigger an open redirect to an external domain depending on the level of validation done by the application prior to returning the `redirect`. > [!NOTE] > This does not impact your React Router application if you are using [Declarative Mode](https://reactrouter.com/start/modes#declarative) (`<BrowserRouter>`)

O3 Security · Impact-Aware SCA

Is GHSA-2j2x-hqr9-3h42 in your dependencies?

O3 detects GHSA-2j2x-hqr9-3h42 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