React Router has XSS Vulnerability

Exploitation

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

CVSS

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

EPSS

• CVE-2025-59057: 0.50% estimated exploitation activity in the next 30 days; percentile 43.12 (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.

A XSS vulnerability exists in in React Router's meta()/<Meta APIs in Framework Mode when generating script:ld+json tags which could allow arbitrary JavaScript execution during SSR if untrusted content is used to generate the tag. [!NOTE] This does not impact applications using Declarative Mode (<BrowserRouter) or Data Mode (createBrowserRouter/<RouterProvider).

Published by the source

8 Jan 2026, 20:42 UTC

Last modified by the source

8 Sep 2026, 16:45 UTC

Source last checked

26 Oct 2026, 13:02 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-3cgp-3xvw-98x8

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-3cgp-3xvw-98x8

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

# Patch Next advisory brief: CVE-2025-59057

Advisory: React Router has XSS Vulnerability
IDs: CVE-2025-59057, GHSA-3cgp-3xvw-98x8
Record: https://patchnext.com/advisories/cve-2025-59057 (revision 2, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.6)
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.9.0; @remix-run/react 2.17.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm react-router: affected >= 7.0.0, <= 7.8.2; fixed in 7.9.0
- npm @remix-run/react: affected >= 1.15.0, <= 2.17.0; fixed in 2.17.1

## 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/react --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/react.
- 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-3cgp-3xvw-98x8 (OSV record GHSA-3cgp-3xvw-98x8 lists affected ranges: npm react-router >=7.0.0 =1.15.0 <2.17.1 (fixed))
- Verified: https://github.com/advisories/GHSA-3cgp-3xvw-98x8 (GitHub-reviewed advisory GHSA-3cgp-3xvw-98x8 lists affected ranges: npm react-router >=7.0.0 =1.15.0 <=2.17.0)

Commands are suggestions: review each one before running it.