How severe is GHSA-qwww-vcr4-c8h2?

No CVSS score has been assigned to GHSA-qwww-vcr4-c8h2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qwww-vcr4-c8h2?

GHSA-qwww-vcr4-c8h2 affects the following packages: react-router (npm), react-router (npm). Ecosystems affected: npm.

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

Update react-router to 7.18.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qwww-vcr4-c8h2 is resolved across your whole dependency graph.

How do I detect GHSA-qwww-vcr4-c8h2 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for react-router, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-qwww-vcr4-c8h2 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-qwww-vcr4-c8h2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-qwww-vcr4-c8h2 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-qwww-vcr4-c8h2 published, and has it been updated?

GHSA-qwww-vcr4-c8h2 was published on July 24, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

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

Fix: remix-run/react-router#15353

GHSA-qwww-vcr4-c8h2 is a security vulnerability in react-router. A fix is available for react-router — see the affected versions and patch details below.

Published

Jul 24, 2026

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

9Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

react-routernpm

68.7Mdownloads / week

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

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`react-router`	≥ 7.12.0&&< 7.18.2	7.18.2`npm install react-router@7.18.2`
📦npm	`react-router`	≥ 8.0.0&&< 8.3.0	8.3.0`npm install react-router@8.3.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for react-router, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update react-router to 7.18.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qwww-vcr4-c8h2 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-qwww-vcr4-c8h2 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works