CVE-2026-53669 — react-router
Fix: remix-run/react-router#15176CVE-2026-53669 is a Open Redirect vulnerability in react-router. A fix is available for react-router — see the affected versions and patch details below.
React Router: Open redirect via backslash in <Link> and useNavigate (CVE-2025-68470 bypass)
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- 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 CVE-2026-53669.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
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.
react-routernpmDescription
This is a follow up to CVE-2025-68470. React Router was alerted to certain scenarios in which the fix there was incomplete so there still existed some scenarios where attacker supplied paths passed to navigation mechanisms could result in unexpected external navigations.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | react-router | ≥ 6.0.0&&< 7.18.0 | 7.18.0npm install react-router@7.18.0 |
Affected Products
react-routershopifyDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for react-router, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update react-router to 7.18.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-53669 is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This Moderate impact open redirect vulnerability in React Router affects multiple Red Hat products. A remote attacker could exploit this by crafting a malicious link that uses backslashes in navigation components, leading to user redirection to arbitrary external websites. This could facilitate phishing attacks…
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.Source: Red Hat security advisory for CVE-2026-53669 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Hardened Images | prometheus3-13-main-3.13.1-0.5.hum1 | RHSA-2026:48780 |
| Red Hat Hardened Images | prometheus3-5-main-3.5.5-0.6.hum1 | RHSA-2026:48799 |
Frequently Asked Questions
Is CVE-2026-53669 in your dependencies?
Find it across npm, including transitive dependencies.