VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

react-router-dom: vulnerability history, versions and safety

react-router-dom is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 120 releases, from Jun 2024 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded C1 M1
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 23 Jul 2026.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in npm →

See all react-router-dom vulnerabilities

Vulert verdict on react-router-dom 7.18.4 i

Updated on 23 Oct 2026

Careful: 7.18.4 was published with malicious code in it, not just a bug. Do not install it.

Package health score 15/100
  • Security Malicious code published
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

The current release contains malicious code, which caps this score.

What to do: Do not resolve 7.18.4 as-is. Check whether you already run an affected release and pin a version the maintainers have re-published. Check what you run: Vulert alerts you when a safe version is published. Monitor it with Vulert →

  • Current release 7.18.4 — affected i
  • Vulnerabilities on record 2 over 2 years · 1 in the last year i
  • Latest disclosure 23 Jul 2026 i
  • Highest CVSS 6.9 i
  • With no published fix 2 i
  • Malicious packages 1 i
  • Depended on by 3,066 packages i
  • Stars 56,611 i
  • OpenSSF scorecard 4/10 i
  • Last release 1 month ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for react-router-dom, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
7.18.4 15 Sep 2026 C1 M1 malicious MIT No Details →
7.18.3 28 Aug 2026 C1 M1 malicious MIT No Details →
6.30.6 18 Aug 2026 C1 M1 malicious MIT No Details →
6.30.5 18 Aug 2026 C1 M1 malicious MIT No Details →
7.18.2 28 Jul 2026 C1 M1 malicious MIT No Details →
7.18.1 29 Jun 2026 C1 M1 malicious MIT No Details →
7.18.0 16 Jun 2026 C1 M1 malicious MIT No Details →
0.0.0-experimental-d07149147 15 Jun 2026 C1 malicious MIT No Details →
7.17.0 04 Jun 2026 C1 M1 malicious MIT No Details →
0.0.0-experimental-dd63c14ca 04 Jun 2026 C1 malicious MIT No Details →
0.0.0-experimental-63fd291ad 04 Jun 2026 C1 malicious MIT No Details →
6.30.4 29 May 2026 C1 M1 malicious MIT No Details →
7.16.0 28 May 2026 C1 M1 malicious MIT No Details →
7.15.1 14 May 2026 C1 M1 malicious MIT No Details →
0.0.0-experimental-abc385596 13 May 2026 C1 malicious MIT No Details →
0.0.0-experimental-073f56f6c 11 May 2026 C1 malicious MIT No Details →
7.15.0 05 May 2026 C1 M1 malicious MIT No Details →
0.0.0-experimental-51412399d 05 May 2026 C1 malicious MIT No Details →
0.0.0-experimental-34996874d 22 Apr 2026 C1 malicious MIT No Details →
7.14.2 21 Apr 2026 C1 M1 malicious MIT No Details →
0.0.0-experimental-689d76079 20 Apr 2026 C1 malicious MIT No Details →
7.14.1 13 Apr 2026 C1 M1 malicious MIT No Details →
0.0.0-nightly-4547c8015-20260410 10 Apr 2026 C1 malicious MIT No Details →
0.0.0-experimental-cb0fdf114 10 Apr 2026 C1 malicious MIT No Details →
0.0.0-experimental-58b44aa83 10 Apr 2026 C1 malicious MIT No Details →
0.0.0-nightly-5ac7a7290-20260404 04 Apr 2026 C1 malicious MIT No Details →
0.0.0-nightly-80c67a953-20260403 03 Apr 2026 C1 malicious MIT No Details →
7.14.0 02 Apr 2026 C1 M1 malicious MIT No Details →
7.14.0-pre.0 31 Mar 2026 C1 M1 malicious MIT No Details →
0.0.0-nightly-fbe4951b9-20260326 26 Mar 2026 C1 malicious MIT No Details →
0.0.0-nightly-44c3d6ba9-20260325 25 Mar 2026 C1 malicious MIT No Details →
0.0.0-nightly-111f3a3f2-20260324 24 Mar 2026 C1 malicious MIT No Details →
7.13.2 23 Mar 2026 C1 M1 malicious MIT No Details →
0.0.0-nightly-18bac808f-20260323 23 Mar 2026 C1 malicious MIT No Details →
0.0.0-nightly-19e1f0f2c-20260321 21 Mar 2026 C1 malicious MIT No Details →
0.0.0-nightly-b897f185f-20260319 19 Mar 2026 C1 malicious MIT No Details →
7.13.2-pre.0 18 Mar 2026 C1 M1 malicious MIT No Details →
0.0.0-nightly-1cd923e38-20260318 18 Mar 2026 C1 malicious MIT No Details →
0.0.0-nightly-7f1014972-20260313 13 Mar 2026 C1 malicious MIT No Details →
0.0.0-nightly-7d21b1c15-20260311 11 Mar 2026 C1 malicious MIT No Details →
0.0.0-nightly-c5012af14-20260305 05 Mar 2026 C1 malicious MIT No Details →
0.0.0-nightly-7990dd5d5-20260303 03 Mar 2026 C1 malicious MIT No Details →
0.0.0-experimental-567b27f71 02 Mar 2026 C1 malicious MIT No Details →
0.0.0-nightly-bbe4a7317-20260228 28 Feb 2026 C1 malicious MIT No Details →
0.0.0-nightly-d8ffb2dbd-20260224 24 Feb 2026 C1 malicious MIT No Details →
7.13.1 23 Feb 2026 C1 M1 malicious MIT No Details →
0.0.0-nightly-5745c4ba3-20260220 20 Feb 2026 C1 malicious MIT No Details →
0.0.0-nightly-db7eb57d1-20260219 19 Feb 2026 C1 malicious MIT No Details →
7.13.1-pre.0 18 Feb 2026 C1 M1 malicious MIT No Details →
0.0.0-nightly-6dda561b4-20260218 18 Feb 2026 C1 malicious MIT No Details →
0.0.0-nightly-b66e632db-20260213 13 Feb 2026 C1 malicious MIT No Details →
0.0.0-experimental-56b72276e 12 Feb 2026 C1 malicious MIT No Details →
0.0.0-experimental-e067e5e52 10 Feb 2026 C1 malicious MIT No Details →
0.0.0-nightly-3f168fb75-20260206 06 Feb 2026 C1 malicious MIT No Details →
0.0.0-nightly-6d4e212a9-20260204 04 Feb 2026 C1 malicious MIT No Details →
0.0.0-nightly-b643537e8-20260130 30 Jan 2026 C1 malicious MIT No Details →
0.0.0-nightly-7ca70609b-20260129 29 Jan 2026 C1 malicious MIT No Details →
0.0.0-experimental-f887449bb 26 Jan 2026 C1 malicious MIT No Details →
0.0.0-nightly-75dc0063d-20260124 24 Jan 2026 C1 malicious MIT No Details →
7.13.0 23 Jan 2026 C1 M1 malicious MIT No Details →
0.0.0-nightly-6324bb4fe-20260122 22 Jan 2026 C1 malicious MIT No Details →
0.0.0-nightly-3126264a6-20260121 21 Jan 2026 C1 malicious MIT No Details →
7.13.0-pre.0 20 Jan 2026 C1 M1 malicious MIT No Details →
0.0.0-nightly-3a5b5ad0e-20260117 17 Jan 2026 C1 malicious MIT No Details →
0.0.0-nightly-f29c6c956-20260116 16 Jan 2026 C1 malicious MIT No Details →
0.0.0-nightly-28605c834-20260113 13 Jan 2026 C1 malicious MIT No Details →
0.0.0-nightly-9987ba0a2-20260109 09 Jan 2026 C1 malicious MIT No Details →
0.0.0-experimental-3fe27584d 08 Jan 2026 C1 malicious MIT No Details →
0.0.0-nightly-c38d76ce4-20260108 08 Jan 2026 C1 malicious MIT No Details →
6.30.3 07 Jan 2026 C1 M1 malicious MIT No Details →
7.12.0 07 Jan 2026 C1 M1 malicious MIT No Details →
0.0.0-nightly-0ef10abcd-20260107 07 Jan 2026 C1 malicious MIT No Details →
6.30.3-pre-v6.0 06 Jan 2026 C1 M1 malicious MIT No Details →
7.12.0-pre.0 06 Jan 2026 C1 M1 malicious MIT No Details →
0.0.0-nightly-041c7b10b-20260106 06 Jan 2026 C1 malicious MIT No Details →
0.0.0-nightly-7394407ae-20251224 24 Dec 2025 C1 malicious MIT No Details →
0.0.0-nightly-30f6c1d81-20251220 20 Dec 2025 C1 malicious MIT No Details →
0.0.0-nightly-915694ead-20251219 19 Dec 2025 C1 malicious MIT No Details →
0.0.0-nightly-7ad685377-20251218 18 Dec 2025 C1 malicious MIT No Details →
7.11.0 17 Dec 2025 C1 M1 malicious MIT No Details →
0.0.0-nightly-60e382aff-20251216 16 Dec 2025 C1 malicious MIT No Details →
7.11.0-pre.0 15 Dec 2025 C1 M1 malicious MIT No Details →
0.0.0-nightly-7c7325139-20251213 13 Dec 2025 C1 malicious MIT No Details →
0.0.0-nightly-0206276a4-20251212 12 Dec 2025 C1 malicious MIT No Details →
0.0.0-experimental-f9e19c91c 12 Dec 2025 C1 malicious MIT No Details →
0.0.0-experimental-653010f49 11 Dec 2025 C1 malicious MIT No Details →
0.0.0-experimental-df9e1151a 11 Dec 2025 C1 malicious MIT No Details →
0.0.0-experimental-22117d3a9 11 Dec 2025 C1 malicious MIT No Details →
0.0.0-nightly-22117d3a9-20251211 11 Dec 2025 C1 malicious MIT No Details →
0.0.0-nightly-4e9bd3504-20251210 10 Dec 2025 C1 malicious MIT No Details →
0.0.0-experimental-2a296c713 09 Dec 2025 C1 malicious MIT No Details →
0.0.0-experimental-6f53aff26 09 Dec 2025 C1 malicious MIT No Details →
0.0.0-experimental-3cde40396 09 Dec 2025 C1 malicious MIT No Details →
0.0.0-nightly-90e07f167-20251206 06 Dec 2025 C1 malicious MIT No Details →
0.0.0-nightly-2f9ffa560-20251205 05 Dec 2025 C1 malicious MIT No Details →
7.10.1 04 Dec 2025 C1 M1 malicious MIT No Details →
0.0.0-nightly-1954672a2-20251204 04 Dec 2025 C1 malicious MIT No Details →
7.10.1-pre.0 03 Dec 2025 C1 M1 malicious MIT No Details →
0.0.0-experimental-f8522255d 03 Dec 2025 C1 malicious MIT No Details →
0.0.0-experimental-bfc808d6c 03 Dec 2025 C1 malicious MIT No Details →
0.0.0-nightly-716be8521-20251203 03 Dec 2025 C1 malicious — No Details →
7.10.0 02 Dec 2025 C1 M1 malicious — No Details →
0.0.0-experimental-112589a91 01 Dec 2025 C1 malicious — No Details →
0.0.0-experimental-303421afa 28 Nov 2025 C1 malicious — No Details →
0.0.0-nightly-c2cb6013d-20251128 28 Nov 2025 C1 malicious — No Details →
7.10.0-pre.1 26 Nov 2025 C1 M1 malicious — No Details →
0.0.0-nightly-8f73c5c73-20251126 26 Nov 2025 C1 malicious — No Details →
7.10.0-pre.0 25 Nov 2025 C1 M1 malicious — No Details →
0.0.0-nightly-75bdd9b9f-20251125 25 Nov 2025 C1 malicious — No Details →
0.0.0-nightly-1dbf8e39b-20251122 22 Nov 2025 C1 malicious — No Details →
0.0.0-experimental-2d8f5c807 21 Nov 2025 C1 malicious — No Details →
0.0.0-nightly-266dc7f4c-20251121 21 Nov 2025 C1 malicious — No Details →
0.0.0-experimental-266dc7f4c 20 Nov 2025 C1 malicious — No Details →
0.0.0-nightly-25d4741fb-20251120 20 Nov 2025 C1 malicious — No Details →
0.0.0-experimental-1a4134895 19 Nov 2025 C1 malicious — No Details →
0.0.0-nightly-6f69b9006-20251118 18 Nov 2025 C1 malicious — No Details →
0.0.0-nightly-dc0e9dc06-20251115 15 Nov 2025 C1 malicious — No Details →
0.0.0-nightly-47896928b-20251114 14 Nov 2025 C1 malicious — No Details →
6.30.2 13 Nov 2025 C1 M1 malicious — No Details →
6.30.2-pre-v6.0 13 Nov 2025 C1 M1 malicious — No Details →

The newest 120 of 1,063 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for react-router-dom

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-53668: React Router and React Router DOM Open Redirect Leading to XSS 6.9 medium No fix published 23 Jul 2026
Malicious code in react-router-dom (npm) N/A critical No fix published 25 Jun 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About react-router-dom

Is react-router-dom safe to use?

Vulert records 2 vulnerabilities for react-router-dom in npm: 1 critical, 0 high, 1 medium and 0 low. 2 of them have no published fix yet, so those are the ones to avoid or mitigate. 1 are malicious-package vulnerabilities: the published package itself contained hostile code, not only a bug.

What is react-router-dom's Vulert package health score?

Vulert scores react-router-dom 15/100, which reads as critical. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release contains malicious code, which caps this score.

Is the latest version of react-router-dom affected?

Yes. 7.18.4, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of react-router-dom should I use?

7.18.4 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does react-router-dom have?

2 vulnerabilities are recorded for react-router-dom in the npm ecosystem: 1 critical, 0 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new react-router-dom vulnerabilities disclosed?

1 vulnerability was recorded for react-router-dom in the last 12 months, and the oldest entry in this database dates to 25 Jun 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of react-router-dom are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

What does a malicious-package vulnerability mean?

It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.

How do I monitor react-router-dom for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the react-router-dom version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.