Skip to main content
Mallory
HighVulnerability

CVE-2026-42211: React Router Framework Mode RCE via Prototype Pollution

Published Jun 2, 2026 · Updated 26 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS8.1High · v3.1
EPSS0.42%36th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Shopify
IdentifiersCVE-2026-42211CWE-502 · Deserialization of Untrusted Data

CVE-2026-42211 affects React Router versions 7.0.0 through 7.14.1 in Framework Mode. The single-fetch deserializer uses a vendored fork of turbo-stream v2 whose TYPE_ERROR handling can invoke arbitrary constructors while reconstructing serialized JavaScript errors. When chained with a separate, existing prototype pollution vulnerability in application code, this behavior can enable unauthorized remote code execution through a two-step attack using external requests. React Router does not itself supply the prerequisite prototype pollution flaw. Applications using Declarative Mode or Data Mode are not affected. Version 7.14.2 fixes the vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can compromise server-side confidentiality, integrity, and availability through arbitrary code execution. An attacker could access application data and credentials, modify data or application behavior, and disrupt service, subject to the permissions and resources available to the application process. The RCE impact depends on successfully chaining the deserialization behavior with an existing prototype pollution flaw.

Mitigation

If you can’t patch tonight, do this now.

Until the update can be deployed, eliminate the prerequisite prototype pollution condition by fixing vulnerable application code and dependencies. Where architecturally feasible, use Declarative Mode with BrowserRouter or Data Mode with createBrowserRouter and RouterProvider, which are not affected.

Remediation

Patch, then assume compromise.

Upgrade React Router to version 7.14.2 or later and redeploy affected applications. Independently identify and fix prototype pollution vulnerabilities in application code and dependencies; the React Router update does not remediate those separate flaws.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
ShopifyReact-Routerapplication
FAQ

Frequently asked questions

Is CVE-2026-42211 exploited in the wild?
As of Oct 22, 2026, Mallory has no reports of CVE-2026-42211 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-42211?
As of Oct 22, 2026, Mallory has found no public exploit for CVE-2026-42211.
Is there a patch for CVE-2026-42211?
Upgrade React Router to version 7.14.2 or later and redeploy affected applications. Independently identify and fix prototype pollution vulnerabilities in application code and dependencies; the React Router update does not remediate those separate flaws.
What products are affected by CVE-2026-42211?
Shopify React-Router.
How severe is CVE-2026-42211?
CVE-2026-42211 has a CVSS v3.1 score of 8.1 (High) and an EPSS score of 0.42% (36th percentile) as of Oct 22, 2026.
Activity feed

Recent activity

12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+3 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity4Community discussion across Reddit, Mastodon, and other social sources.