# CVE-2026-53668: React Router: Open redirect can lead to XSS

> Attackers can exploit open redirects in React Router to trigger XSS, requiring applications to allow such redirects.

- **Severity:** Medium 6.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Jul 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-jjmj-jmhj-qwj2, MINI-9qj2-vf4w-748c, MINI-jqvq-p9qw-hc7h

## What is CVE-2026-53668?

CVE-2026-53668 is a medium-severity vulnerability in remix-run react-router, published on 27 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

React Router is a router for React. In versions 6.30.2 through 6.30.4 and 7.9.6 through 7.12.0, applications that allow open redirects are vulnerable to XSS. An attacker could craft a malicious link that redirects users to an unexpected external site or that exploits an XSS vector.This issue has been fixed in version 7.13.0.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2026-53668?

4 open source packages ship an affected version, including react-router and react-router-dom. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `react-router` | npm | From 7.9.6 | 7.13.0 |
| `react-router` | npm | From 7.9.6 | 7.13.0 |
| `react-router-dom` | npm | From 6.30.2 | 6.30.6 |
| `react-router-dom` | npm | From 6.30.2 | 6.30.6 |

Products: Shopify React-Router.

## How do I fix CVE-2026-53668?

Upgrade react-router to 7.13.0 or later.

## Is CVE-2026-53668 being exploited?

There is no known exploitation of CVE-2026-53668 in the wild and no public exploit code.

## Other vulnerabilities in remix-run react-router

- [CVE-2026-55685](https://insights.sbomify.com/CVE-2026-55685/): React Router: Unauthenticated Denial of Service via Inefficient Route Matching (high 8.7)
- [CVE-2026-21884](https://insights.sbomify.com/CVE-2026-21884/): React Router SSR XSS in ScrollRestoration (high 8.2)
- [CVE-2026-42211](https://insights.sbomify.com/CVE-2026-42211/): React Router's vendored turbo-stream v2 allows arbitrary constructor invocation via TYPE_ERROR deserialization leading to Unauth RCE (high 8.1)
- [CVE-2026-33245](https://insights.sbomify.com/CVE-2026-33245/): React Router vulnerable to XSS in unstable RSC redirect handling via javascript: redirect targets (high 8.0)
- [CVE-2026-22029](https://insights.sbomify.com/CVE-2026-22029/): React Router vulnerable to XSS via Open Redirects (high 8.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53668 and fix it if it is affected.

What it is: CVE-2026-53668 is a medium-severity vulnerability in remix-run react-router, published on 27 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-53668 in the wild and no public exploit code.

Affected packages and fixed versions:
- react-router (npm): affected from 7.9.6; fixed in 7.13.0
- react-router (npm): affected from 7.9.6; fixed in 7.13.0
- react-router-dom (npm): affected from 6.30.2; fixed in 6.30.6
- react-router-dom (npm): affected from 6.30.2; fixed in 6.30.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53668/ (Markdown: https://insights.sbomify.com/CVE-2026-53668/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53668
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53668
- OSV: https://osv.dev/vulnerability/CVE-2026-53668

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53668/
Summaries are generated and may contain mistakes; the official description above is the record.