The team behind React Router has disclosed seven React Router vulnerabilities at once. The advisories appeared on GitHub on November 18, 2026, at around 17:45 UTC. Major versions 6, 7 and 8 are affected, and with them frameworks built on React Router, such as Remix 2 and Shopify Hydrogen. Four of the flaws are rated high and three medium. Updates are available for versions 7 and 8, while two flaws remain unpatched for React Router 6.
React Router vulnerabilities: the seven advisories at a glance
The security advisories in the React Router GitHub repository describe the flaws in deliberately brief terms. No CVE IDs had been assigned at the time of publication. The advisories in detail:
- GHSA-2rq8-3rm6-2w8f, denial of service in server-side route discovery (high, CVSS 7.5): specially crafted requests can consume excessive server resources. Framework mode with server-side rendering and lazy route discovery enabled is affected, as are the still unstable RSC modes. Fixed in react-router 7.18.5 and 8.5.1.
- GHSA-qhgm-jj2j-75wj, prototype pollution in data deserialization (high, CVSS 7.4): attacker-controlled serialized data can pollute object prototypes and interfere with application behavior. Exploitation requires attacker influence over the serialized data processed by the affected decoder. Framework mode is affected. Fixed in 7.18.5 and 8.5.1.
- GHSA-mp5r-736v-j8x9, denial of service in Node.js request handling (high, CVSS 7.5): a vulnerable dependency in @react-router/node, @react-router/serve and @react-router/dev can let crafted requests terminate the server process. Fixed in 7.18.6 (node and serve) and 8.3.1.
- GHSA-x8j4-g9rr-8j87, denial of service in route matching (high): crafted paths can cause excessive CPU consumption, in the browser or on the server depending on where matching runs. All modes from version 6.0.0 are affected. Fixed in 7.18.3 and 8.3.1.
- GHSA-mjj8-rxh9-q8f5, cross-site scripting in RSC redirects (medium, CVSS 4.7): only affects the experimental React Server Components modes when an application uses untrusted input as a redirect destination. Fixed in 7.18.4 and 8.4.0.
- GHSA-8wpx-2pj4-ggvx, CSRF bypass in server-side actions (medium): a flaw in origin validation may allow cross-site request forgery under certain deployment and cookie configurations. Fixed in 7.18.3 and 8.3.1.
- GHSA-7m2v-44vx-v55w, open redirect in loader and action responses (medium): applications that use untrusted redirect destinations can send users to attacker-controlled sites, for example for phishing. Affected from version 6.4.0. Fixed in 7.18.3 and 8.3.1.
Some patches have been out for weeks
The order of events stands out. According to the npm registry, most fixes shipped long before the advisories: react-router 7.18.3 and 8.3.1 on August 28, 7.18.4 and 8.4.0 on September 15, and 7.18.5 and 8.5.1 on October 27. The only new release on November 18 was version 7.18.6 of @react-router/node and @react-router/serve. Teams that update dependencies regularly may therefore already be protected. Those who pin versions should check now.
The advisories do not mention active exploitation. Experience shows, however, that publishing details increases the risk of attackers scanning for unpatched applications, especially for denial-of-service flaws that are reachable without authentication.
Which versions are safe
All seven flaws are fixed in:
- React Router 8: react-router 8.5.1 or later, plus @react-router/node, @react-router/serve and @react-router/dev 8.5.1 or later.
- React Router 7: react-router 7.18.5 or later, plus @react-router/node and @react-router/serve 7.18.6 or later.
The situation is harder for React Router 6 and therefore for Remix 2. According to the advisory from hosting provider Netlify, there is no patched 6.x release for the route-matching denial of service and the open redirect. A simple npm update will not help. Closing these two flaws requires migrating to React Router 7 or 8, which means moving Remix 2 projects to React Router 7.
How developers can check their projects
Netlify has published detailed guidance that also applies to other environments:
- List installed versions: after
npm install, runningnpm ls react-router @react-router/node @react-router/serve @react-router/devshows every copy, including those a framework brings in. With pnpm, usepnpm why; with Yarn,yarn why. - Watch for nested copies: if another package such as react-router-dom or a framework pins a specific version, updating react-router alone is not enough. The parent package needs updating.
- Ship the lockfile: commit package.json and the lockfile together, then redeploy.
- Remember old deploys: preview deploys and older production deploys keep running the old code until they are deleted.
- Check an environment variable: React Router sets IS_RR_BUILD_REQUEST only during builds. It should never be set in production. According to Netlify, the prototype pollution flaw only matters on the server if this build-only setting is present at runtime.
Regardless of the update, Netlify recommends validating redirect destinations taken from user input, such as a returnTo parameter, in application code. A Strict-Transport-Security header, ideally with an entry on the HSTS preload list, adds protection against the CSRF flaw. According to Netlify, an attack requires that content can be served over plain HTTP on the site’s own domain.
Hosting makes a difference
How exposed an application is also depends on the platform. Netlify says the denial-of-service flaws have limited impact there thanks to its autoscaling serverless architecture, although attacks could increase function costs. Netlify does not use the built-in Node.js server of @react-router/serve, and its adapter does not support the RSC modes. Teams running React Router on their own Node.js server, by contrast, are directly exposed to all server-side flaws.
The cluster of fixes recalls the Next.js security updates in early November, which also closed several flaws in caching and server features at once, as covered in our article on the Next.js security release. Server-side rendering and server components move logic back to the server, and with that the attack surface of classic web applications grows again. How deep such problems can run was shown recently by the Java4Shell flaw in OpenJDK.
Assessment
Taken individually, the seven flaws are not a disaster. According to the advisories, none directly allows code execution on the server. Together, though, they add up to a clear task for anyone running React Router 7 or 8: update to 7.18.5 or 8.5.1 or later, do not forget the Node packages, and clean up old deploys. For projects on React Router 6 and Remix 2, the disclosure is one more reason not to postpone the migration any longer.




