dbcve.org
React Router\/nodeFramework / library · Shopify

CVE-2025-61686

CRITICAL · 9.1 CVSS v3.1 Published 2026-01-10
Fix available
A fix is available. Upgrade to 2.17.2 / 7.9.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 @react-router/node versions 7.0.0 through 7.9.3, @remix-run/deno prior to version 2.17.2, and @remix-run/node prior to version 2.17.2, if createFileSessionStorage() is being used from @react-router/node (or @remix-run/node/@remix-run/deno in Remix v2) with an unsigned cookie, it is possible for an attacker to cause the session to try to read/write from a location outside the specified session file directory. The success of the attack would depend on the permissions of the web server process to access those files. Read files cannot be returned directly to the attacker. Session file reads would only succeed if the file matched the expected session file format. If the file matched the session file format, the data would be populated into the server side session but not directly returned to the attacker unless the application logic returned specific session information. This issue has been patched in @react-router/node version 7.9.4, @remix-run/deno version 2.17.2, and @remix-run/node version 2.17.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

A path traversal vulnerability exists in React Router's and Remix's file session storage. When createFileSessionStorage() is used with an unsigned (untrusted) cookie, attackers can manipulate the session to read or write files outside the intended session directory. Successful exploitation depends on the web server process permissions and requires the targeted file to match the expected session file format.

MitigationUpgrade to @react-router/node 7.9.4, @remix-run/node 2.17.2, or @remix-run/deno 2.17.2. Additionally, ensure signed cookies are used in production rather than unsigned cookies to prevent tampering.

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 Router\/nodeFramework / library
Affected:>= 7.0.0, < 7.9.4
Remix Run\/denoApplication
Affected:< 2.17.2
Remix Run\/nodeApplication
Affected:< 2.17.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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

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

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. Identify installed package version
    Run 'npm list @react-router/node' or 'npm list @remix-run/node' or 'npm list @remix-run/deno' depending on your framework to see the exact version installed
    Affected if The version is >= 7.0.0 and < 7.9.4 for @react-router/node, or < 2.17.2 for @remix-run/node or @remix-run/deno
  2. Locate createFileSessionStorage usage
    Search your codebase for 'createFileSessionStorage' to see if this function is being used to handle sessions
    Affected if createFileSessionStorage is in use and the version is in the affected range
  3. Verify session cookie signing configuration
    Examine your session configuration where createFileSessionStorage is called and check if a 'cookie' option with a 'secrets' or 'signed' property is configured
    Affected if No secret key is configured for the session cookie, meaning cookies are unsigned and can be tampered with by attackers
  4. Inspect session cookie handling in requests
    Check how session data is read in your routes using getSession() and commitSession() - verify if the session cookie value comes directly from an unsigned source
    Affected if Session cookies are not cryptographically signed and their values can be externally manipulated

You are affected if you use a vulnerable version of @react-router/node, @remix-run/node, or @remix-run/deno with createFileSessionStorage and your session cookies are not signed with a secret key.

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.2 / 7.9.4 or later
Fixed in 2.17.27.9.4
Interim mitigation

Upgrade to @react-router/node 7.9.4, @remix-run/node 2.17.2, or @remix-run/deno 2.17.2. Additionally, ensure signed cookies are used in production rather than unsigned cookies to prevent tampering.

Recommended fix High confidence

@react-router/[email protected] OR @remix-run/[email protected] OR @remix-run/[email protected]

  1. Identify which React Router or Remix Run package is in use (@react-router/node, @remix-run/node, or @remix-run/deno)
  2. Run the appropriate package manager update command: npm install @react-router/[email protected], npm install @remix-run/[email protected], or npm install @remix-run/[email protected]
  3. Verify the updated version is installed by checking package.json or running npm list <package-name>
  4. Test the application to ensure session handling works correctly after the upgrade
  5. Ensure session cookies are signed in production (the vulnerability only affects unsigned cookies)
Caveat Patch releases typically have minimal breaking changes; review the changelog for any behavioral changes between your current version and 7.9.4/2.17.2

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

Fix this in React Router\/node Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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