# GHSA-qwww-vcr4-c8h2: React Router: RSC Mode CSRF Bypass Allows Action Execution Before 400 Response

> Attackers can bypass CSRF protections in unstable RSC mode to execute actions before a 400 response, affecting applications using these experimental APIs.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Jul 2026

## What is GHSA-qwww-vcr4-c8h2?

GHSA-qwww-vcr4-c8h2 is a vulnerability in react-router, published on 24 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

This is a follow up to CVE-2026-22030 to address related CSRF flows in unstable RSC code paths.

> [!NOTE]
> This only affects your application if you are using the unstable RSC APIs

## Which versions are affected by GHSA-qwww-vcr4-c8h2?

4 open source packages ship an affected version, including react-router.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `react-router` | npm | From 7.12.0 | 7.18.2 |
| `react-router` | npm | From 7.12.0 | 7.18.2 |
| `react-router` | npm | From 8.0.0 | 8.3.0 |
| `react-router` | npm | From 8.0.0 | 8.3.0 |

## How do I fix GHSA-qwww-vcr4-c8h2?

Upgrade react-router to a fixed version for your release line: 7.18.2 or 8.3.0.

## Is GHSA-qwww-vcr4-c8h2 being exploited?

There is no known exploitation of GHSA-qwww-vcr4-c8h2 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-qwww-vcr4-c8h2 and fix it if it is affected.

What it is: GHSA-qwww-vcr4-c8h2 is a vulnerability in react-router, published on 24 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-qwww-vcr4-c8h2 in the wild and no public exploit code.

Affected packages and fixed versions:
- react-router (npm): affected from 7.12.0; fixed in 7.18.2
- react-router (npm): affected from 7.12.0; fixed in 7.18.2
- react-router (npm): affected from 8.0.0; fixed in 8.3.0
- react-router (npm): affected from 8.0.0; fixed in 8.3.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-qwww-vcr4-c8h2/ (Markdown: https://insights.sbomify.com/GHSA-qwww-vcr4-c8h2/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-qwww-vcr4-c8h2

---
From sbomify Insights: https://insights.sbomify.com/GHSA-qwww-vcr4-c8h2/
Summaries are generated and may contain mistakes; the official description above is the record.