dbcve.org
React RouterFramework / library · Shopify

CVE-2025-59057

HIGH · 7.6 CVSS v3.1 Published 2026-01-10
Fix available
A fix is available. Upgrade to after 7.8.2 or later.
See remediation →
80/100
Remediation priority · High
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
React Router is a router for React. In @remix-run/react versions 1.15.0 through 2.17.0. and react-router versions 7.0.0 through 7.8.2, 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. There is no impact if the application is being used in Declarative Mode (<BrowserRouter>) or Data Mode (createBrowserRouter/<RouterProvider>). This issue has been patched in @remix-run/react version 2.17.1 and react-router version 7.9.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

XSS vulnerability in React Router's meta()/<Meta> APIs during SSR in Framework Mode allows arbitrary JavaScript execution via script:ld+json tags when untrusted content is used. Only affects Framework Mode; Declarative Mode and Data Mode are unaffected.

MitigationUpgrade to @remix-run/react 2.17.1 or react-router 7.9.0, or audit and sanitize any untrusted content used in meta tags.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
React RouterFramework / library
Affected:>= 7.0.0, <= 7.8.2
Remix Run\/reactFramework / library
Affected:>= 1.15.0, <= 2.17.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check your installed @remix-run/react version
    Run `npm list @remix-run/react` or check package.json for the @remix-run/react dependency version
    Affected if Version is >= 1.15.0 and <= 2.17.0
  2. Check your installed react-router version
    Run `npm list react-router` or check package.json for the react-router dependency version
    Affected if Version is >= 7.0.0 and <= 7.8.2 (Shopify React Router)
  3. Confirm you are using Framework Mode
    Verify your app does NOT use <BrowserRouter> (Declarative Mode) or createBrowserRouter/<RouterProvider> (Data Mode). Check your entry.server.tsx or main app file for how the router is configured
    Affected if You are using Framework Mode (server.ts with createRequestHandler) rather than Declarative or Data Mode
  4. Identify if meta() or <Meta> component generates script:ld+json
    Search your codebase for `meta()` function definitions or `<Meta>` component usage, and check if any return objects contain `script:ld+json` property
    Affected if Your code generates script:ld+json tags via the meta API
  5. Check if untrusted input flows into meta() for ld+json
    Review all meta() return values that include script:ld+json and trace whether any values come from user input, URL parameters, or external APIs without sanitization
    Affected if Untrusted or user-supplied data is passed into script:ld+json meta tags

You are affected if you use an affected version of @remix-run/react (1.15.0-2.17.0) or react-router (7.0.0-7.8.2), run in Framework Mode, and pass untrusted input to script:ld+json via the meta() API.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 7.8.2
Interim mitigation

Upgrade to @remix-run/react 2.17.1 or react-router 7.9.0, or audit and sanitize any untrusted content used in meta tags.

Recommended fix High confidence

react-router 7.9.0 or @remix-run/react 2.17.1

  1. Identify which routing library is in use: react-router (7.x) or @remix-run/react (1.x-2.x)
  2. For React Router 7.x: Update package.json to specify react-router version 7.9.0 or higher
  3. For @remix-run/react: Update package.json to specify @remix-run/react version 2.17.1 or higher
  4. Run npm install or yarn to install the updated package
  5. Verify the updated version is installed by checking node_modules/react-router/package.json or node_modules/@remix-run/react/package.json
  6. Test the application to ensure the meta()/<Meta> APIs function correctly in Framework Mode

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in React Router Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59057 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59057 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data