CVE-2026-21884: remix-run react-router · Cross-site Scripting
Affects remix-run react-routerSource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 7.12.0 soon.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 7.12.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade remix-run react-router to 7.12.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| remix-runreact-router | Affected
| Fixed in– |
npmreact-routerpkg:npm/react-routerOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability has been officially fixed in react-router version 7.12.0 and @remix-run/react version 2.17.3. Users should upgrade to these versions or later to remediate the issue. If server-side rendering in Framework Mode is disabled, or if Declarative Mode (<BrowserRouter>) or Data Mode (createBrowserRouter/<RouterProvider>) is used, there is no impact. No additional mitigations are required beyond applying the official patches.
Description
React Router is a router for React. In @remix-run/react version prior to 2.17.3. and react-router 7.0.0 through 7.11.0, a XSS vulnerability exists in in React Router's <ScrollRestoration> API in Framework Mode when using the getKey/storageKey props during Server-Side Rendering which could allow arbitrary JavaScript execution during SSR if untrusted content is used to generate the keys. There is no impact if server-side rendering in Framework Mode is disabled, or if Declarative Mode (<BrowserRouter>) or Data Mode (createBrowserRouter/<RouterProvider>) is being used. This issue has been patched in @remix-run/react version 2.17.3 and react-router version 7.12.0.
References
- github.com/remix-run/react-router/security/advisories/GHSA-8v8x-cx79-35w7 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-21884 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2428421 (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-21884.json (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:3958 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:3960 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:3782 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:19712 (opens in a new tab)