Quick answers
- Is CVE-2026-22030 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-22030 being exploited in the wild.
- How severe is CVE-2026-22030?
- Medium severity, with a CVSS score of 6.5, published 8 January 2026.
- Which products and versions are affected?
- @remix-run/server-runtime (npm) <= 2.17.2, SEMVER:introduced=0,fixed=2.17.3; Remix Server-Runtime <= 2.17.2.
- Is there a fix for CVE-2026-22030?
- Yes. @remix-run/server-runtime (npm): upgrade to 2.17.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-22030 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-22030?
- Check whether you run @remix-run/server-runtime (npm) or Remix Server-Runtime at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @remix-run/server-runtime (npm): upgrade to 2.17.3 or later
npm install @remix-run/server-runtime@2.17.3
Technical details
A Cross-Site Request Forgery (CSRF) vulnerability exists in React Router (and Remix v2) due to improper origin validation during the processing of document POST requests. The issue specifically affects applications using server-side route 'action' handlers in Framework Mode or React Server Actions in unstable RSC modes. An attacker can exploit this by inducing a victim to submit a cross-origin request, leading to unauthorized state changes on the server. Applications using Declarative Mode or Data Mode are not affected. Patches are available in react-router version 7.12.0 and @remix-run/server-runtime version 2.17.3.
Affected products
- remix-run react-router >= 7.0.0, <= 7.11.0
- remix-run @remix-run/server-runtime <= 2.17.2
Identifiers
- CVE-2026-22030
- GHSA-h5cw-625j-3rxh
Timeline
- 2026-01-08: disclosed
- 2026-01-08: advisory
- 2026-01-08: patched