React Router vulnerable to XSS via Open Redirects

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.0 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N

EPSS

• CVE-2026-22029: 0.87% estimated exploitation activity in the next 30 days; percentile 58.74 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 developers are creating redirect paths from untrusted content or via an open redirect. [!NOTE] This does not impact applications that use Declarative Mode (<BrowserRouter).

Published by the source

8 Jan 2026, 20:54 UTC

Last modified by the source

3 Feb 2026, 03:15 UTC

Source last checked

26 Oct 2026, 12:41 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-2w69-qvjg-hvjx

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-2w69-qvjg-hvjx

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-22029

Advisory: React Router vulnerable to XSS via Open Redirects
IDs: CVE-2026-22029, GHSA-2w69-qvjg-hvjx
Record: https://patchnext.com/advisories/cve-2026-22029 (revision 2, source checked 26 Oct 2026, 12:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: react-router 7.12.0; @remix-run/router 1.23.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm react-router: affected >= 7.0.0, <= 7.11.0; fixed in 7.12.0
- npm @remix-run/router: affected <= 1.23.1; fixed in 1.23.2

## Suggested inspection (read-only)
- `npm ls react-router --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @remix-run/router --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on react-router, @remix-run/router.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-2w69-qvjg-hvjx (OSV record GHSA-2w69-qvjg-hvjx lists affected ranges: npm react-router >=7.0.0 =0 <1.23.2 (fixed))
- Verified: https://github.com/advisories/GHSA-2w69-qvjg-hvjx (GitHub-reviewed advisory GHSA-2w69-qvjg-hvjx lists affected ranges: npm react-router >=7.0.0 =0 <=1.23.1)

Commands are suggestions: review each one before running it.