Skip to main content
CVE-2026-22030VulnerabilityPublished Updated

CVE-2026-22030: remix-run react-router · Origin Validation Error

Affects remix-run react-routerSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium : upgrade to 7.12.0 when convenient.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% 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:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-26.

What to do

Upgrade remix-run react-router to 7.12.0.

Affected software

ProductAffectedFixed in
remix-runreact-routerAffected
  • =@remix-run/router < 2.17.3
  • =react-router >= 7.0.0, < 7.12.0
Fixed in–
npmreact-routerpkg:npm/react-routerOther threatsAffected
  • <7.12.0
Fixed in
  • 7.12.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate upgrade to react-router version 7.12.0 or later and @remix-run/server-runtime version 2.17.3 or later to apply the official patches addressing the origin validation issue. 2. Review application routing configurations to avoid using Framework Mode or unstable React Server Components modes if possible, or ensure that origin validation is properly enforced. 3. Implement additional CSRF protections at the application level, such as anti-CSRF tokens, SameSite cookies, and strict CORS policies to reduce attack surface. 4. Educate developers on secure usage patterns of React Router and Remix frameworks, emphasizing the security implications of different routing modes. 5. Conduct thorough security testing, including penetration testing and code reviews focused on CSRF and origin validation mechanisms. 6. Monitor user activity and logs for unusual POST requests or patterns indicative of CSRF attempts. 7. For organizations unable to immediately patch, consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block suspicious POST requests targeting UI routes. 8. Maintain awareness of updates from the remix-run project and community advisories for any further developments or exploit reports.

Description

React Router is a router for React. In @remix-run/server-runtime version prior to 2.17.3.and react-router 7.0.0 through 7.11.0, React Router (or Remix v2) is vulnerable to CSRF attacks on document POST requests to UI routes when using server-side route action handlers in Framework Mode, or when using React Server Actions in the new unstable RSC modes. There is no impact if Declarative Mode (<BrowserRouter>) or Data Mode (createBrowserRouter/<RouterProvider>) is being used. This issue has been patched in @remix-run/server-runtime version 2.17.3 and react-router version 7.12.0.

References

Community reviews

Loading reviews…