CVE-2025-61686
criticalpriority · track · 16EPSS 0.173 · 97 %ileexploit · PoCEUUSEPSS · scored 2026-10-27
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
exploits (3)
Public proof-of-concept and weaponised exploit code.
- FlowerWitch/CVE-2025-61686_dockerCVE-2025-61686复现的dockerfile与pocPoC · poc_in_github
affected products (9)
Products and version ranges known to be affected.
advisories (1)
Vendor and ecosystem advisories describing this.
- GHSA-9583-h5hc-x8cwReact Router has Path Traversal in File Session Storage2026-01-08ghsa · osvUS
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 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.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (7)
External citations — patches, advisories, analysis.
- https://github.com/remix-run/react-router/security/advisories/GHSA-9583-h5hc-x8cwcnnvd
- https://reactrouter.com/Patchcnnvd
- https://github.com/remix-run/react-router/security/advisories/GHSA-9583-h5hc-x8cwenisa_euvd
- https://access.redhat.com/security/cve/CVE-2025-61686nvd
- https://bugzilla.redhat.com/show_bug.cgi?id=2428423nvd
- https://github.com/remix-run/react-router/security/advisories/GHSA-9583-h5hc-x8cwThird Party Advisorynvd
- https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-61686.jsonnvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan