React Router is a router for React. From 7.12.0 until 7.15.1, certain CSRF checks in React Router v7 Framework Mode were insufficient and run on POST requests, but were bypassed on PUT/PATCH/DELETE requests. This is a low severity vulnerability because modern browser protections (CORS preflight, SameSite cookies) already block the cross-origin attack vectors that this missing CSRF check would otherwise gate. This vulnerability is fixed in 7.15.1.
CVE-2026-53663
This low-severity CVE scores 3.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.1
- EG Score
- 3.1(medium)
- EPSS
- 1.3%
- KEV
- Not listed
Published
June 15, 2026
Last Modified
June 23, 2026
References (1)
- security-advisories@githubhttps://github.com/remix-run/react-router/security/advisories/GHSA-84g9-w2xq-vcv6
Vendor Advisories for CVE-2026-53663(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 1 ecosystem)
npm(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| react-router | — | 7.15.1 | — |
| @remix-run/server-runtime | — | 2.17.5 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 20× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-07 00:18 UTCEG score recompute
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 18:29 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 19:06 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 19:46 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-24 20:25 UTCEG score recompute
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-21 18:58 UTCEG score recompute
- 2026-06-18 19:28 UTCEG score recompute
- 2026-06-15 20:11 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-53663?
When was CVE-2026-53663 disclosed?
Is CVE-2026-53663 actively exploited?
What is the CVSS score of CVE-2026-53663?
How do I remediate CVE-2026-53663?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53663
Is Your Infrastructure Affected by CVE-2026-53663?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.