CVE-2025-68470: CWE-601: URL Redirection to Untrusted Site ('Open Redirect') in remix-run react-router
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.
AI Analysis
Technical Summary
CVE-2025-68470 is a security vulnerability classified under CWE-601 (URL Redirection to Untrusted Site, commonly known as an open redirect) affecting the React Router library, a widely used routing solution for React applications. The vulnerability exists in versions 6.0.0 through 6.30.1 and 7.0.0 through 7.9.5. It arises when an attacker crafts a malicious URL path that, when processed by React Router's navigation functions such as navigate(), <Link>, or redirect(), causes the application to redirect the user to an external URL controlled by the attacker. This behavior is problematic when the application passes untrusted or user-supplied input directly into these navigation paths without proper validation or sanitization. The vulnerability enables attackers to perform phishing attacks or redirect users to malicious sites, potentially leading to credential theft or malware distribution. The issue does not require user interaction but does require that the application code improperly handle untrusted navigation inputs. The vulnerability has been addressed in React Router versions 6.30.2 and 7.9.6 by implementing stricter validation of navigation paths to prevent external redirects. The CVSS 3.1 score of 6.5 reflects a medium severity, with a network attack vector, low attack complexity, and requiring privileges (likely developer or application-level privileges) but no user interaction. No known exploits have been reported in the wild as of the publication date (January 10, 2026).
Potential Impact
For European organizations, this vulnerability poses a significant risk primarily to web applications built using the affected versions of React Router. If these applications accept untrusted input for navigation paths without proper validation, attackers can exploit this flaw to redirect users to malicious websites. This can facilitate phishing campaigns, credential harvesting, or distribution of malware, undermining user trust and potentially leading to data breaches or financial losses. The impact is especially critical for sectors with high web application usage such as finance, e-commerce, healthcare, and government services. Additionally, organizations relying on single-page applications (SPAs) using React Router may inadvertently expose their users to these risks. Although the vulnerability does not directly compromise confidentiality or availability, the integrity of user navigation and trust is compromised, which can have downstream effects on organizational reputation and compliance with data protection regulations like GDPR. The medium severity score indicates a moderate risk that can escalate if combined with other vulnerabilities or social engineering tactics.
Mitigation Recommendations
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. The primary mitigation is to upgrade React Router to versions 6.30.2 or 7.9.6, where the vulnerability is patched. Developers must ensure that any user-supplied or untrusted input used in navigation paths is strictly validated or sanitized to prevent external URLs from being used in navigation functions. Implementing a whitelist of allowed internal routes or using URL parsing libraries to verify that navigation targets remain within the application's domain can effectively prevent exploitation. Additionally, security teams should monitor application logs for unusual redirect patterns and consider deploying web application firewalls (WAFs) with rules to detect and block suspicious redirect attempts. User education on phishing risks and multi-factor authentication can further reduce the impact of successful redirection attacks. Finally, organizations should integrate secure coding practices and static code analysis to detect improper handling of navigation inputs in future development.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Italy, Spain, Poland
CVE-2025-68470: CWE-601: URL Redirection to Untrusted Site ('Open Redirect') in remix-run react-router
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.
AI-Powered Analysis
Technical Analysis
CVE-2025-68470 is a security vulnerability classified under CWE-601 (URL Redirection to Untrusted Site, commonly known as an open redirect) affecting the React Router library, a widely used routing solution for React applications. The vulnerability exists in versions 6.0.0 through 6.30.1 and 7.0.0 through 7.9.5. It arises when an attacker crafts a malicious URL path that, when processed by React Router's navigation functions such as navigate(), <Link>, or redirect(), causes the application to redirect the user to an external URL controlled by the attacker. This behavior is problematic when the application passes untrusted or user-supplied input directly into these navigation paths without proper validation or sanitization. The vulnerability enables attackers to perform phishing attacks or redirect users to malicious sites, potentially leading to credential theft or malware distribution. The issue does not require user interaction but does require that the application code improperly handle untrusted navigation inputs. The vulnerability has been addressed in React Router versions 6.30.2 and 7.9.6 by implementing stricter validation of navigation paths to prevent external redirects. The CVSS 3.1 score of 6.5 reflects a medium severity, with a network attack vector, low attack complexity, and requiring privileges (likely developer or application-level privileges) but no user interaction. No known exploits have been reported in the wild as of the publication date (January 10, 2026).
Potential Impact
For European organizations, this vulnerability poses a significant risk primarily to web applications built using the affected versions of React Router. If these applications accept untrusted input for navigation paths without proper validation, attackers can exploit this flaw to redirect users to malicious websites. This can facilitate phishing campaigns, credential harvesting, or distribution of malware, undermining user trust and potentially leading to data breaches or financial losses. The impact is especially critical for sectors with high web application usage such as finance, e-commerce, healthcare, and government services. Additionally, organizations relying on single-page applications (SPAs) using React Router may inadvertently expose their users to these risks. Although the vulnerability does not directly compromise confidentiality or availability, the integrity of user navigation and trust is compromised, which can have downstream effects on organizational reputation and compliance with data protection regulations like GDPR. The medium severity score indicates a moderate risk that can escalate if combined with other vulnerabilities or social engineering tactics.
Mitigation Recommendations
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. The primary mitigation is to upgrade React Router to versions 6.30.2 or 7.9.6, where the vulnerability is patched. Developers must ensure that any user-supplied or untrusted input used in navigation paths is strictly validated or sanitized to prevent external URLs from being used in navigation functions. Implementing a whitelist of allowed internal routes or using URL parsing libraries to verify that navigation targets remain within the application's domain can effectively prevent exploitation. Additionally, security teams should monitor application logs for unusual redirect patterns and consider deploying web application firewalls (WAFs) with rules to detect and block suspicious redirect attempts. User education on phishing risks and multi-factor authentication can further reduce the impact of successful redirection attacks. Finally, organizations should integrate secure coding practices and static code analysis to detect improper handling of navigation inputs in future development.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2025-12-18T13:48:59.555Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6961c40f19784dcf52ace867
Added to database: 1/10/2026, 3:14:23 AM
Last enriched: 1/10/2026, 3:31:11 AM
Last updated: 1/10/2026, 11:41:50 PM
Views: 15
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-0824: Cross Site Scripting in questdb ui
MediumCVE-2025-13393: CWE-918 Server-Side Request Forgery (SSRF) in marceljm Featured Image from URL (FIFU)
MediumCVE-2025-12379: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in averta Shortcodes and extra features for Phlox theme
MediumCVE-2026-0822: Heap-based Buffer Overflow in quickjs-ng quickjs
MediumCVE-2026-0821: Heap-based Buffer Overflow in quickjs-ng quickjs
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.