CSRF Bypass Vulnerability in React Router: Action Execution Before 400 Response

react-router Updated 24 Jul 2026

Summary

24/07/2026
HIGH
Yes i
High
7.1

GHSA-qwww-vcr4-c8h2: React Router: RSC Mode CSRF Bypass Allows Action Execution Before 400 Response. Affects react-router versions >= 7.12.0, < 8.3.0. Fixed in 8.3.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

React Router is a popular routing library for React applications, enabling developers to create dynamic single-page applications with ease. It provides features such as nested routing, route matching, and code splitting. However, certain unstable APIs within React Router have been found to be vulnerable to Cross-Site Request Forgery (CSRF) attacks, particularly in the RSC (React Server Components) mode, which can lead to unauthorized action execution.

Vulnerability Detail

The vulnerability arises from a flaw in the unstable RSC code paths of React Router, allowing attackers to bypass CSRF protections. This means that an attacker could potentially execute actions on behalf of a user before the application receives a 400 response, leading to unauthorized operations. The issue is particularly concerning for applications utilizing the unstable RSC APIs, as it exposes them to risks of data manipulation and unauthorized access.

How To Fix

Latest published version: 8.5.0 as of 23 Oct 2026

npm install react-router@8.5.0

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

8.3.0

This is the first release that contains the fix.

npm install react-router@8.3.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, developers can implement additional CSRF protection mechanisms, such as validating CSRF tokens on the server side for sensitive actions, until the package is updated. This can help mitigate the risk of unauthorized actions being executed.

Conclusion

In summary, the CSRF bypass vulnerability in React Router's unstable RSC mode poses a significant risk to applications using affected versions. It is crucial to update to version 8.3.0 or later to ensure the security of your application. Additionally, utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for react-router →

Share this vulnerability

FAQ

The CVSS score of this vulnerability is 7.1, indicating a high severity level.

Versions of React Router from 7.12.0 to 8.2.9 are affected by this vulnerability.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

If exploited, this vulnerability could allow attackers to execute unauthorized actions on behalf of users, leading to data manipulation and security breaches.

Yes, implementing additional CSRF protection mechanisms, such as server-side validation of CSRF tokens, can help mitigate the risk until the package is updated.

Related vulnerabilities

Recent vulnerabilities recorded for react-router.

How To Fix

Latest published version: 8.5.0 as of 23 Oct 2026

npm install react-router@8.5.0

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

8.3.0

This is the first release that contains the fix.

npm install react-router@8.3.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback