VulnerabilityPublished 10 Jan 2026Updated 12 Jan 2026

CVE-2025-68470: remix-run react-router · Open Redirect

Affects remix-run react-routerSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 7.9.6 or 6.30.2 when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 7.9.6, 6.30.2

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade remix-run react-router to 7.9.6 or 6.30.2.

Affected software

Product	Affected	Fixed in
remix-runreact-router	Affected >=7.0.0 <7.9.6	Fixed in 7.9.6
remix-runreact-router	Affected >=6.0.0 <6.30.2	Fixed in 6.30.2
npmreact-router`pkg:npm/react-router`Other threats	Affected 6.0.0 <=6.30.1 7.0.0 <=7.9.5	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately audit their web applications to identify usage of React Router versions between 6.0.0 and 6.30.1 or 7.0.0 and 7.9.5. Upgrading to patched versions 6.30.2 or 7.9.6 is the primary and most effective mitigation. Additionally, developers must ensure that all navigation paths and URLs passed to React Router's navigation functions are properly validated and sanitized to reject or neutralize untrusted input. Implement strict input validation policies, employing allowlists for URLs or path segments where feasible. Employ Content Security Policy (CSP) headers to restrict the domains to which the browser can navigate or load resources, reducing the impact of potential redirects. Conduct security code reviews focusing on navigation logic and user input handling. Educate developers about the risks of open redirects and secure coding practices. Monitor web traffic for unusual redirect patterns and implement user awareness training to recognize phishing attempts that may leverage this vulnerability. Finally, maintain an inventory of third-party libraries and ensure timely patching of dependencies.

Description

React Router is a router for React. In versions 6.0.0 through 6.30.1 and 7.0.0 through 7.9.5, an attacker-supplied path can be crafted so that when a React Router application navigates to it via navigate(), <Link>, or redirect(), the app performs a navigation/redirect to an external URL. This is only an issue if you are passing untrusted content into navigation paths in your application code. This issue has been patched in versions 6.30.2 and 7.9.6.

Impact

For European organizations, this vulnerability can lead to significant security risks if exploited. Web applications using vulnerable React Router versions that improperly handle user input in navigation paths may redirect users to malicious external sites controlled by attackers. This can facilitate phishing campaigns targeting employees or customers, potentially leading to credential compromise, unauthorized access, or malware infections. The integrity of user navigation is compromised, undermining trust in affected applications. While the vulnerability does not directly impact confidentiality or availability, the indirect consequences of successful phishing or malware delivery can be severe. Organizations in sectors with high reliance on web applications, such as finance, e-commerce, and government services, are particularly at risk. The requirement for passing untrusted input means that secure coding practices can mitigate risk, but legacy or poorly maintained applications remain vulnerable. The lack of known exploits reduces immediate risk, but the medium severity score and widespread use of React Router in European web development environments warrant prompt remediation.

CWE-601URL Redirection to Untrusted Site ('Open Redirect') (opens in a new tab)
Base weaknessLikelihood of exploit: LowOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
Use an intermediate disclaimer page that provides the user with a clear warning that they are leaving the current site. Implement a long timeout before the redirect occurs, or force the user to click on the link. Be careful to avoid XSS problems (CWE-79) when generating the disclaimer page.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
OWASP Cheat Sheets
Mass Assignment (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V5.1.5 (opens in a new tab)
Attack patterns
Cross-Site Flashing (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/remix-run/react-router/security/advisories/GHSA-9jcx-v3wj-wh4m (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Jan 2026, 07:50 UTC

WeaknessesCWE-601

Technical details

References

Community reviews

Related threats