How severe is CVE-2026-22029?

CVE-2026-22029 has a CVSS score of 8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-22029?

CVE-2026-22029 affects the following packages: react-router (npm), @remix-run/router (npm). Ecosystems affected: npm.

How do I fix CVE-2026-22029?

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.

How do I detect CVE-2026-22029 in my npm dependencies?

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.

How do I mitigate CVE-2026-22029 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2026-22029 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-22029 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 CVE-2026-22029?

CVE-2026-22029 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 58th 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 CVE-2026-22029?

CVE-2026-22029 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-22029 published, and has it been updated?

CVE-2026-22029 was published on January 10, 2026 and was last updated on October 28, 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

Not in CISA KEV

HIGH severity

CVE-2026-22029 — react-router

HIGH

CVE-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

Also known asGHSA-2w69-qvjg-hvjx

Published

Jan 10, 2026

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk-0.01%

Lower risk than most CVEs58th percentile — riskier than 58% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

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.

9Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

react-routernpm

33.1Mdownloads / week

@remix-run/routernpm

11.6Mdownloads / week

Description

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

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`react-router`	≥ 7.0.0&&< 7.12.0	7.12.0`npm install react-router@7.12.0`
📦npm	`@remix-run/router`	all versions	1.23.2`npm install @remix-run/router@1.23.2`

Affected Products

2 products · 2 configurations

Application

react-routershopify

≥ 7.0.0 && ≤ 7.11.0

range

Application

remix-run\/reactshopify

< 1.23.2

range

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, 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
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

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.

Red HatImportant

Workaround published by Red Hat

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-22029 (CC BY 4.0)

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.10	`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

O3 Security · Impact-Aware SCA

Is CVE-2026-22029 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works