dbcve.org
React RouterFramework / library · Shopify

CVE-2026-22030

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-10
Fix available
A fix is available. Upgrade to 2.17.3 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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/server-runtime version prior to 2.17.3. and react-router 7.0.0 through 7.11.0, React Router (or Remix v2) is vulnerable to CSRF attacks on document POST requests to UI routes when using server-side route action handlers in Framework Mode, or when using React Server Actions in the new unstable RSC modes. There is no impact if Declarative Mode (<BrowserRouter>) or Data Mode (createBrowserRouter/<RouterProvider>) is being used. This issue has been patched in @remix-run/server-runtime version 2.17.3 and react-router version 7.12.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

React Router versions prior to 2.17.3 (and react-router 7.0.0-7.11.0) are vulnerable to CSRF attacks on document POST requests to UI routes when using server-side route action handlers in Framework Mode or React Server Actions in unstable RSC modes. The vulnerability does not impact Declarative Mode or Data Mode configurations.

MitigationUpgrade @remix-run/server-runtime to version 2.17.3 or react-router to version 7.12.0 or later. If upgrading is not feasible, ensure the application is using Declarative Mode or Data Mode which are not affected by this vulnerability.

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.11.0
Remix Run\/reactFramework / library
Affected:< 2.17.3

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 react-router version in package.json
    Inspect your package.json file and locate the react-router dependency. Note the installed version number.
    Affected if The version is 7.0.0 through 7.11.0 (inclusive)
  2. Check @remix-run/server-runtime version in package.json
    Inspect your package.json file and locate the @remix-run/server-runtime dependency. Note the installed version number.
    Affected if The version is below 2.17.3
  3. Identify if Framework Mode is in use
    Review your React Router v7 configuration files and runtime setup to determine whether the application is running in Framework Mode.
    Affected if Framework Mode is enabled AND the react-router version is affected (7.0.0-7.11.0)
  4. Identify if React Server Actions in unstable RSC modes are in use
    Review your application code and configuration to determine whether React Server Actions are being used in unstable RSC (React Server Components) modes.
    Affected if React Server Actions in unstable RSC modes are enabled AND the react-router or @remix-run/server-runtime version is affected
  5. Confirm configuration mode is Declarative or Data Mode
    Review your application configuration to identify which mode is active: Declarative Mode, Data Mode, or Framework Mode.
    Affected if The application is NOT using Declarative Mode or Data Mode (meaning it is using the affected Framework Mode or unstable RSC)
  6. Determine if server-side route action handlers are in use
    Inspect your route handler code to identify if document POST requests are being processed through server-side route action handlers.
    Affected if Server-side route action handlers are processing POST requests to UI routes AND the version and mode conditions are met

Your environment is affected if you are using react-router 7.0.0-7.11.0 or @remix-run/server-runtime below 2.17.3 AND you have Framework Mode or React Server Actions in unstable RSC modes enabled (not Declarative Mode or Data Mode).

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

Upgrade @remix-run/server-runtime to version 2.17.3 or react-router to version 7.12.0 or later. If upgrading is not feasible, ensure the application is using Declarative Mode or Data Mode which are not affected by this vulnerability.

Recommended fix High confidence

react-router 7.12.0 or @remix-run/server-runtime 2.17.3

  1. Identify which product is in use: React Router 7.x (react-router package) or Remix Run/react (@remix-run/server-runtime package)
  2. For React Router 7.x: Update react-router to version 7.12.0 or later in package.json
  3. For Remix Run/react: Update @remix-run/server-runtime to version 2.17.3 or later in package.json
  4. Run npm install, yarn install, or pnpm install to install the updated package
  5. Verify the installed version matches the fixed release
  6. Test the application, particularly any POST requests to UI routes using server-side actions or React Server Actions in RSC modes
  7. Ensure no regression in functionality, especially if using Framework Mode or unstable RSC modes

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

Fix this in React Router Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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