CVE-2025-43864: React Router allows a DoS via cache poisoning by forcing SPA mode
Summary After some research, it turns out that it is possible to force an application to switch to SPA mode by adding a header to the request. If the application uses SSR and is forced to switch to SPA, this causes an error that completely corrupts the page.
Published Apr 24, 2025 · Updated Apr 25, 2025
Affected packages
react-router
- Ecosystem
- npm
- Affected
- >= 7.2.0, <= 7.5.1
- Fixed in
- 7.5.2
- Check
npm ls react-router
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
After some research, it turns out that it is possible to force an application to switch to SPA mode by adding a header to the request. If the application uses SSR and is forced to switch to SPA, this causes an error that completely corrupts the page. If a cache system is in place, this allows the response containing the error to be cached, resulting in a cache poisoning that strongly impacts the availability of the application.
Details
The vulnerable header is X-React-Router-SPA-Mode; adding it to a request sent to a page/endpoint using a loader throws an error. Here is the vulnerable code :
To use the header, React-router must be used in Framework mode, and for the attack to be possible the target page must use a loader.
Steps to reproduce
Versions used for our PoC:
- "@react-router/node": "^7.5.0",
- "@react-router/serve": "^7.5.0",
- "react": "^19.0.0"
- "react-dom": "^19.0.0"
- "react-router": "^7.5.0"
- Install React-Router with its default configuration in Framework mode (https://reactrouter.com/start/framework/installation)
- Add a simple page using a loader (example:
routes/ssr)
image
- Send a request to the endpoint using the loader (
/ssrin our case) adding the following header:
X-React-Router-SPA-Mode: yesNotice the difference between a request with and without the header;
Normal request Capture d’écran 2025-04-07 à 08 36 27
With the header Capture d’écran 2025-04-07 à 08 37 01 image
Impact
If a system cache is in place, it is possible to poison the response by completely altering its content (*by an error message*), strongly impacting its availability, making the latter impractical via a cache-poisoning attack.
Credits
- Rachid Allam (zhero;)
- Yasser Allam (inzo_)
Credited to cold-try.
References
- https://github.com/remix-run/react-router/security/advisories/GHSA-f46r-rw29-r322
- https://github.com/remix-run/react-router/commit/c84302972a152d851cf5dd859ff332b354b70111
- https://github.com/remix-run/react-router/blob/e6c53a0130559b4a9bd47f9cf76ea5b08a69868a/packages/react-router/lib/server-runtime/server.ts#L407
- https://nvd.nist.gov/vuln/detail/CVE-2025-43864
- https://github.com/advisories/GHSA-f46r-rw29-r322
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-55685
React Router: Unauthenticated Denial of Service via Inefficient Route Matching
high8.7Jul 24, 2026GHSA-qwww-vcr4-c8h2
React Router: RSC Mode CSRF Bypass Allows Action Execution Before 400 Response
high7.1Jul 24, 2026CVE-2026-53666
React Router: Arbitrary Constructor Injection via deserializeErrors() in React Router SSR Hydration
medium6.1Jul 23, 2026CVE-2026-53667
React Router: RSCErrorHandler Missing Protocol Validation (XSS)
medium6.9Jul 23, 2026CVE-2026-53668
React Router: Open redirect leading to XSS
medium6.9Jul 23, 2026CVE-2026-53669
React Router: Open redirect via backslash in <Link> and useNavigate (CVE-2025-68470 bypass)
medium5.1Jul 23, 2026
