CVE-2025-68470
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedReact Router is a router for React. In versions 6.0.0 through 6.30.1 and 7.0.0 through 7.9.5, an attacker-supplied path can be crafted so that when a React Router application navigates to it via navigate(), <Link>, or redirect(), the app performs a navigation/redirect to an external URL. This is only an issue if you are passing untrusted content into navigation paths in your application code. This issue has been patched in versions 6.30.2 and 7.9.6.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is an open redirect vulnerability in React Router where untrusted user input passed to navigate(), <Link>, or redirect() components can cause the application to redirect to attacker-controlled external URLs instead of internal routes.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 6.0.0, <= 6.30.1>= 7.0.0, <= 7.9.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check React Router versionRun 'npm list react-router' or 'npm list react-router-dom' to see installed version, or inspect package.json dependenciesAffected if version is 6.0.0-6.30.1 or 7.0.0-7.9.5
-
Identify navigate() calls with user inputSearch codebase for 'navigate(' calls and inspect whether the argument could be controlled by user input (query params, form inputs, API responses)Affected if user-supplied values are passed directly to navigate() without validation
-
Identify <Link> components with user inputSearch for <Link> elements and inspect the 'to' prop for dynamic values from user input sourcesAffected if the 'to' prop contains unsanitized user-controlled data
-
Identify redirect() usage with user inputSearch for 'redirect(' calls in code and check if the argument derives from user input without validationAffected if user input is passed directly to redirect() function
Environment is affected if React Router version is within 6.0.0-6.30.1 or 7.0.0-7.9.5 AND the codebase passes unvalidated user input to navigate(), <Link>, or redirect() functions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate React Router to version 6.30.2 or 7.9.6, and audit all code paths where user-supplied values are used in navigation functions to ensure proper validation before use.
React Router 6.30.2 (for 6.x users) or React Router 7.9.6 (for 7.x users)
- Identify your current React Router version by checking package.json
- If using React Router 6.x (>= 6.0.0, <= 6.30.1): run `npm install react-router-dom@^6.30.2` or `yarn add react-router-dom@^6.30.2`
- If using React Router 7.x (>= 7.0.0, <= 7.9.5): run `npm install react-router-dom@^7.9.6` or `yarn add react-router-dom@^7.9.6`
- Verify the installation succeeded by checking the installed version: `npm list react-router-dom` or `yarn list react-router-dom`
- Test your application's navigation flows (navigate(), <Link>, redirect()) to ensure functionality is intact
- Review your application code to ensure untrusted content is not being passed directly into navigation paths, as the vulnerability description notes this is only exploitable when doing so
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68470 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-68470 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data