Skip to content
FIRERUN.

The BaaS & deploy-platform newsroom for builders

Subscribe

Netlify

React Router Discloses Seven Bugs, Two With No Fix for Remix 2

Update React Router to 7.18.6 or 8.5.1 and delete old deploys. Seven advisories came out Nov. 18, and Remix 2 apps get no patch for two of them.

Abstract flat-vector editorial illustration for "React Router Discloses Seven Bugs, Two With No Fix for Remix 2"

The React Router team published seven security advisories on Nov. 18, and two of them have no patched release for React Router 6, the version every Remix 2 app runs on. Netlify told customers the same day to update and redeploy, and warned that older deploys keep serving the vulnerable code (Netlify changelog, Nov. 18, 2026).

Key Takeaways

  • React Router 7 apps need react-router 7.18.5 or later, and 7.18.6 for @react-router/node and @react-router/serve.
  • React Router 8 apps need 8.5.1 or later across react-router and the @react-router/ packages.
  • React Router 6 and Remix 2 apps have to move to version 7 to close two of the seven.
  • Delete old previews and branch deploys by hand.

What Was Disclosed

The project’s GitHub advisory page lists seven entries dated Nov. 18. Four are rated high: a denial of service in server-side rendering, a denial of service in route matching, a denial of service in the Node.js request handler and a prototype pollution bug in data deserialization. Three are rated moderate: cross-site scripting in redirects under the experimental React Server Components modes, a CSRF bypass and an open redirect.

Netlify’s table gives the affected ranges. The route-matching bug reaches back to react-router 6.0.0 and the open redirect to 6.4.0. For those two, Netlify said, “there is no patched React Router 6.x release” and npm update cannot fix them. Remix 2 uses React Router 6, so those apps “need to move to React Router 7.”

Most of the fixes predate the disclosure. Netlify lists 7.18.3 and 8.3.1 as the fix for three of the seven, and npm registry timestamps date those releases to Aug. 28. Version 7.18.5 followed on Oct. 27 and only 7.18.6 arrived on Nov. 18.

What Netlify Says It Blocks

Netlify said most of the seven have limited effect on its platform. A crashed function does not take down other requests, it said, but “active exploitation could increase your function costs.” Netlify does not run React Router’s bundled Node.js server and its adapter does not support the experimental server components modes, so it counts two advisories as not affecting its projects.

That assessment covers Netlify only. Netlify said the route-matching bug can also slow a visitor’s browser during client-side navigation on any host.

What to Do

List the installed packages first. Netlify recommends npm ls react-router @react-router/node @react-router/serve @react-router/dev, because a framework can pull in a copy that package.json never names. Update, list again and commit the lockfile.

Next, look for an environment variable named IS_RR_BUILD_REQUEST on the site and in the team’s shared variables. React Router sets it during builds. Netlify said the prototype pollution bug reaches the server only when that variable is present at runtime, and that a site with it configured should remove it and publish a new deploy.

Then delete the old deploys. Netlify never automatically deletes the most recent successful deploy of each branch, so in its words branch deploys “can stay vulnerable indefinitely.” Teams with auto publishing locked have to publish the patched build themselves.

Upgrading fixes the open redirect in React Router’s own navigation. Netlify said app code should still check that a returnTo destination stays on the site.

The Take

This is Firerun’s read, not Netlify’s. The two unpatched advisories turn a routine dependency bump into a migration for Remix 2 teams, and one of the two is rated high. The last React Router 6 release on npm is 6.30.6 from Aug. 18. Teams on Remix 2 should treat this advisory list as the end of security fixes for that line.

Stay in the loop

Get new articles in your inbox

We'll only email you when a new article drops. Unsubscribe anytime.