← Back
CVE-2026-53663
low
CVSS 3.1
Cross-Site Request Forgery (CSRF) in react-router (CVE-2026-53663)
Summary
vulnerability in react-router (CVE-2026-53663). Risk of unauthorized operations or information disclosure. Exploitable via ``createBrowserRouter``. Mitigation: upgrade to `7.15.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-53663** has been found in react-router.
Attackers can target a specific entry point like ``createBrowserRouter`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.1/10.
What to do: upgrade react-router to **7.15.1** or later.
If unsure, ask your IT team or search "react-router CVE-2026-53663" on the vendor's site.
CVE-2026-53663 (react-router) — CWE-352 / CVSS v3 3.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `createBrowserRouter`
Patched: `7.15.1` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**CSRF** (CWE-352) exists in react-router. Attackers reach the vulnerable code path via ``createBrowserRouter`` without authentication.
📍 Affected scope
react-router — . Attack surface: `createBrowserRouter`.
🔥 Severity
Severity: Low (CVSS 3.1/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **7.15.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'react-router' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'react-router' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `react-router` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade react-router to 7.15.1ステージング環境で 7.15.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
react-router
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.15.1"}]}]
npm
@remix-run/server-runtime
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.17.5"}]}]