Categories
CVE-2026-53669 medium CVSS 6.1

Open Redirect in react-router (CVE-2026-53669)

Summary

Vulnerability in react-router (CVE-2026-53669). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 7.18.0 or later.

Original description

The description as published by the source.

React Router is a router for React. Versions 6.0.0 through 7.17.0 are vulnerable to Open Redirtect through use of backslashes in and useNavigate. This issue is a follow up to CVE-2025-68470 and has been fixed in version 7.18.0.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-53669 has been found in react-router.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade react-router to 7.18.0 or later.
If unsure, ask your IT team or search "react-router CVE-2026-53669" on the vendor's site.

CVE-2026-53669 (react-router) — CWE-601 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Patched: 7.18.0 — 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

A vulnerability (CWE-601) exists in react-router.

📍 Affected scope

Check the vendor advisory for the affected versions of react-router.

🔥 Severity

Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 7.18.0.

🛡️ 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'react-router' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で react-router を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade react-router to 7.18.0

    ステージング環境で 7.18.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm react-router
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.18.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details