Quick answers
- Is CVE-2025-59414 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-59414 being exploited in the wild.
- How severe is CVE-2025-59414?
- Low severity, with a CVSS score of 3.1, published 17 September 2025.
- Which products and versions are affected?
- nuxt (npm) SEMVER:introduced=3.6.0,fixed=3.19.0.
- Is there a fix for CVE-2025-59414?
- Yes. nuxt (npm): upgrade to 3.19.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-59414 attacked?
- It is attacked over the network.
- Am I affected by CVE-2025-59414?
- Check whether you run nuxt (npm) 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
- nuxt (npm): upgrade to 3.19.0 or later
npm install nuxt@3.19.0
Technical details
A client-side path traversal vulnerability exists in Nuxt's Island payload revival mechanism (revive-payload.client.ts). During prerendering, if an API endpoint returns user-controlled data with a crafted __nuxt_island object containing path traversal sequences in the "key" field, the client will deserialize this payload and attempt to fetch /__nuxt_island/${key}.json, potentially traversing to unintended endpoints. The attack requires three conditions: prerendering enabled, attacker control over an API response called during prerendering, and client-side navigation to the prerendered page. The vulnerability is mitigated by strict validation of Island keys (alphanumeric with hyphens, max 100 chars). Patches are available in Nuxt 3.19.0+ and 4.1.0+.
Affected products
- Nuxt Nuxt 3.6.0-3.18.x, 4.0.0-4.0.x
Identifiers
- CVE-2025-59414
- GHSA-p6jq-8vc4-79f6
Timeline
- 2025-09-17: disclosed: Advisory published
- 2025-09-17: patched: Patch released in versions 3.19.0 and 4.1.0