How severe is GHSA-84g9-w2xq-vcv6?

GHSA-84g9-w2xq-vcv6 has a CVSS score of 3.1/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-84g9-w2xq-vcv6?

GHSA-84g9-w2xq-vcv6 affects the following packages: react-router (npm), @remix-run/server-runtime (npm). Ecosystems affected: npm.

How do I fix GHSA-84g9-w2xq-vcv6?

Update react-router to 7.15.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-84g9-w2xq-vcv6 is resolved across your whole dependency graph.

How do I detect GHSA-84g9-w2xq-vcv6 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for react-router. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-84g9-w2xq-vcv6 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.

How does O3 Security protect against GHSA-84g9-w2xq-vcv6?

O3 pinpoints whether GHSA-84g9-w2xq-vcv6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-84g9-w2xq-vcv6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-84g9-w2xq-vcv6 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.

What type of vulnerability is GHSA-84g9-w2xq-vcv6?

GHSA-84g9-w2xq-vcv6 is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-84g9-w2xq-vcv6 published, and has it been updated?

GHSA-84g9-w2xq-vcv6 was published on June 15, 2026 and was last updated on June 18, 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

GHSA-84g9-w2xq-vcv6

LOW

GHSA-84g9-w2xq-vcv6 is a low-severity (CVSS 3.1) Cross-Site Request Forgery (CSRF) vulnerability in react-router. O3 Security confirms whether GHSA-84g9-w2xq-vcv6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

React Router: Potential CSRF via PUT/PATCH/DELETE document requests

Also known asCVE-2026-53663

Published

Jun 15, 2026

Updated

Jun 18, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

react-routernpm

50.0Mdownloads / week

@remix-run/server-runtimenpm

1.3Mdownloads / week

Description

Certain CSRF checks in React Router v7 Framework Mode were insufficient and run on POST requests, but were bypassed on PUT/PATCH/DELETE requests. This is a low severity vulnerability because modern browser protections (CORS preflight, SameSite cookies) already block the cross-origin attack vectors that this missing CSRF check would otherwise gate.

[!NOTE] This does not impact your React Router application if you are using Declarative Mode (<BrowserRouter>) or Data Mode (createBrowserRouter/<RouterProvider>).

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`react-router`	≥ 7.12.0&&< 7.15.1	7.15.1
📦npm	`@remix-run/server-runtime`	≥ 2.17.3&&< 2.17.5	2.17.5

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update react-router to 7.15.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-84g9-w2xq-vcv6 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.
How O3 protects you
O3 pinpoints whether GHSA-84g9-w2xq-vcv6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-84g9-w2xq-vcv6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Certain CSRF checks in React Router v7 [Framework Mode]() were insufficient and run on POST requests, but were bypassed on PUT/PATCH/DELETE requests. This is a low severity vulnerability because modern browser protections (CORS preflight, SameSite cookies) already block the cross-origin attack vectors that this missing CSRF check would otherwise gate. > [!NOTE] > This does not impact your React Router application if you are using [Declarative Mode](https://reactrouter.com/start/modes#framework) (`<BrowserRouter>`) or [Data Mode](https://reactrouter.com/start/modes#data) (`createBrowserRouter

O3 Security · Impact-Aware SCA

Is GHSA-84g9-w2xq-vcv6 in your dependencies?

O3 detects GHSA-84g9-w2xq-vcv6 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works