CVE-2026-22029 — react-router
HIGHCVE-2026-22029 is a high-severity (CVSS 8) Cross-site Scripting (XSS) vulnerability in react-router. A fix is available for react-router — see the affected versions and patch details below.
React Router vulnerable to XSS via Open Redirects
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- 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-22029.
EPSS Exploitation Probability
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.
How urgent is this, really
CVE-2026-22029 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
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-routernpm@remix-run/routernpmDescription
React Router is a router for React. In @remix-run/router version prior to 1.23.2 and react-router 7.0.0 through 7.11.0, React Router (and Remix v1/v2) SPA open navigation redirects originating from loaders or actions in Framework Mode, Data Mode, or the unstable RSC modes can result in unsafe URLs causing unintended javascript execution on the client. This is only an issue if you are creating redirect paths from untrusted content or via an open redirect. There is no impact if Declarative Mode (<BrowserRouter>) is being used. This issue has been patched in @remix-run/router version 1.23.2 and react-router version 7.12.0.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | react-router | ≥ 7.0.0&&< 7.12.0 | 7.12.0npm install react-router@7.12.0 |
| 📦npm | @remix-run/router | all versions | 1.23.2npm install @remix-run/router@1.23.2 |
Detection & 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.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-22029 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-22029 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-22029. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Ansible Automation Platform 2.5 for RHEL 8 | automation-gateway-0:2.5.20260225-1.el8ap | RHSA-2026:3959 |
| Red Hat Ansible Automation Platform 2.6 for RHEL 9 | automation-platform-ui-0:2.6.6-1.el9ap | RHSA-2026:3958 |
| multicluster engine for Kubernetes 2.1 | multicluster-engine/console-mce-rhel9:1777128790 | RHSA-2026:13542 |
| multicluster engine for Kubernetes 2.6 | multicluster-engine/console-mce-rhel9:1776223790 | RHSA-2026:9848 |
| multicluster engine for Kubernetes 2.7 | multicluster-engine/console-mce-rhel9:1773100128 | RHSA-2026:5636 |
| multicluster engine for Kubernetes 2.8 | multicluster-engine/console-mce-rhel9:1775116156 | RHSA-2026:8218 |
| Red Hat Advanced Cluster Management for Kubernetes 2.11 | rhacm2/console-rhel9:1783350952 | RHSA-2026:41064 |
| Red Hat Advanced Cluster Management for Kubernetes 2.12 | rhacm2/console-rhel9:1773259174 | RHSA-2026:5633 |
Frequently Asked Questions
Is CVE-2026-22029 in your dependencies?
O3 Security finds CVE-2026-22029 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.