Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

GHSA-9583-h5hc-x8cw — @react-router/node

CRITICAL

GHSA-9583-h5hc-x8cw is a critical-severity (CVSS 9.1) Path Traversal vulnerability in @react-router/node. EPSS puts its 30-day exploitation probability at 17.6% (97th percentile). A fix is available for @react-router/node — see the affected versions and patch details below.

React Router has Path Traversal in File Session Storage

Also known asCVE-2025-61686
Published
Jan 8, 2026
Updated
Sep 18, 2026
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-9583-h5hc-x8cw.

EPSS Exploitation Probability

via FIRST.org ↗
17.6%probability of exploitation in next 30 days
Moderate Risk0.00%
Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-9583-h5hc-x8cw plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 379,145 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

3 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

82other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
@react-router/nodenpm
1.7Mdownloads / week
@remix-run/nodenpm
600Kdownloads / week
@remix-run/denonpm
2Kdownloads / week

Description

If applications use createFileSessionStorage() 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.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
📦npm@react-router/node≥ 7.0.0&&< 7.9.47.9.4npm install @react-router/node@7.9.4
📦npm@remix-run/nodeall versions2.17.2npm install @remix-run/node@2.17.2
📦npm@remix-run/denoall versions2.17.2npm install @remix-run/deno@2.17.2

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @react-router/node, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update @react-router/node to 7.9.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9583-h5hc-x8cw is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-9583-h5hc-x8cw can be triaged on real exposure rather than presence alone.

Tailored to GHSA-9583-h5hc-x8cw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

If applications use `createFileSessionStorage()` from `@react-router/node` (or `@remix-run/node`/`@remix-run/deno` in Remix v2) with an [**unsigned cookie**](https://reactrouter.com/explanation/sessions-and-cookies#signing-cookies), 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 expe
O3 Security · Impact-Aware SCA

Is GHSA-9583-h5hc-x8cw in your dependencies?

O3 Security finds GHSA-9583-h5hc-x8cw across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-9583-h5hc-x8cw: @react (Critical 9.1) | O3 Security