CVE-2026-53721
RCE in Nuxt via route-rule bypass (case-sensitivity mismatch).
Is CVE-2026-53721 being exploited?
Not confirmed. CVE-2026-53721 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.40% probability of exploitation in the next 30 days.
How severe is CVE-2026-53721?
CVE-2026-53721 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-53721?
Yes. A fix has been recorded for CVE-2026-53721. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-53721 affect?
CVE-2026-53721 affects Nuxt.js 3.11.0–3.21.6, Nuxt.js 4.0.0–4.4.6. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-53721?
Upgrade to 3.21.7 or 4.4.7+ now
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via bypassing route rules in Nuxt apps.
Immediate action required
- affected>= 3.11.0 and < 3.21.7
- affected>= 4.0.0 and < 4.4.7
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.