dbcve.org
React RouterFramework / library · Shopify

CVE-2026-33244

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-02
Fix available
A fix is available. Upgrade to 7.13.2 or later.
See remediation →
58/100
Remediation priority · Elevated
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 versions 7.5.1 through 7.13.1, when using Framework Mode with pre-rendering enabled, improper neutralization of the HTTP `Location` header value can permit Cross-Site Scripting (XSS) in the statically generated HTML files if the redirect location comes from an untrusted source. This does not impact applications using Declarative Mode (`<BrowserRouter>`) or Data Mode (`createBrowserRouter/<RouterProvider>`). This is patched in version 7.13.2.

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

React Router versions 7.5.1-7.13.1 contain an XSS vulnerability in Framework Mode when pre-rendering is enabled. The HTTP Location header value is not properly neutralized before being embedded in statically generated HTML files, allowing script injection when redirects originate from untrusted sources. This only affects Framework Mode; Declarative Mode and Data Mode are unaffected.

MitigationUpgrade React Router to version 7.13.2 or later. If immediate upgrade is not feasible, disable pre-rendering in Framework Mode as a temporary workaround.

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.5.1, < 7.13.2

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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 installed React Router version
    Run 'npm list @react-router/node' or 'npm list react-router' to see the installed version. If using Yarn or pnpm, use the equivalent command. Look for @react-router/node or react-router package version.
    Affected if Version is >= 7.5.1 and < 7.13.2
  2. Confirm Framework Mode is in use
    Look for a react-router.config.ts or react-router.config.js file in your project root. Check if 'future' configuration contains 'v3_fetcherPersist: true' or similar Framework Mode indicators, or check package.json for @react-router/* packages.
    Affected if Framework Mode configuration files are present and the project uses @react-router packages
  3. Verify pre-rendering is enabled
    Check your react-router.config.ts/js file for 'prerender: true' in route configurations, or check for routes.ts/routes.js with prerender exports. Also inspect any build configuration files (vite.config.ts, package.json scripts) for pre-rendering related build commands.
    Affected if Pre-rendering is explicitly enabled in route or build configuration
  4. Identify redirect locations in the application
    Search codebase for redirect() calls, particularly in loaders, actions, or middleware. Look for cases where redirect locations may come from user input, external APIs, or database values rather than static trusted paths.
    Affected if Application has redirect() calls with dynamic or unvalidated location values

You are affected if your React Router version is between 7.5.1 and 7.13.1 (exclusive of 7.13.2), Framework Mode is enabled, pre-rendering is turned on, and redirects can originate from untrusted sources.

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 7.13.2 or later
Fixed in 7.13.2
Interim mitigation

Upgrade React Router to version 7.13.2 or later. If immediate upgrade is not feasible, disable pre-rendering in Framework Mode as a temporary workaround.

Recommended fix High confidence

7.13.2

  1. Run `npm install [email protected]` to upgrade to the patched version, or run `npm install react-router@latest` to get the most recent stable release
  2. Verify the upgrade by checking the installed version with `npm list react-router`
  3. If using a lock file (package-lock.json or yarn.lock), commit the updated lockfile changes
  4. Test the application, particularly any redirects in Framework Mode with pre-rendering enabled, to confirm the fix works correctly

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

Fix this in React Router Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33244 — 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-2026-33244 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