CVE-2025-59414: Nuxt has Client-Side Path Traversal in Nuxt Island Payload Revival
Summary A client-side path traversal vulnerability in Nuxt's Island payload revival mechanism allowed attackers to manipulate client-side requests to different endpoints within the same application domain when specific prerendering conditions are met.
Published Sep 17, 2025 · Updated Sep 18, 2025
Affected packages
nuxt
- Ecosystem
- npm
- Affected
- >= 3.6.0, < 3.19.0
- Fixed in
- 3.19.0
- Check
npm ls nuxt
nuxt
- Ecosystem
- npm
- Affected
- >= 4.0.0, < 4.1.0
- Fixed in
- 4.1.0
- Check
npm ls nuxt
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
A client-side path traversal vulnerability in Nuxt's Island payload revival mechanism allowed attackers to manipulate client-side requests to different endpoints within the same application domain when specific prerendering conditions are met.
Technical Details
The vulnerability occurs in the client-side payload revival process (revive-payload.client.ts) where Nuxt Islands are automatically fetched when encountering serialized __nuxt_island objects. The issue affects the following flow:
- During prerendering, if an API endpoint returns user-controlled data containing a crafted
__nuxt_islandobject - This data gets serialized with
devalue.stringifyand stored in the prerendered page - When a client navigates to the prerendered page,
devalue.parsedeserializes the payload - The Island reviver attempts to fetch
/__nuxt_island/${key}.jsonwherekeycould contain path traversal sequences
Prerequisites for Exploitation
This vulnerability requires all of the following conditions:
- Prerendered pages: The application must use Nuxt's prerendering feature (
nitro.prerender) - Attacker-controlled API responses: The attacker must be able to control the response content of an API endpoint that is called during prerendering via
useFetch,useAsyncData, or similar composables - Client-side navigation: A user must navigate to the prerendered page (not during initial SSR hydration)
Attack Scenario
// Malicious API response during prerendering
{
"__nuxt_island": {
"key": "../../../../internal/service",
"params": { "action": "probe" }
}
}This could cause the client to make requests to /__nuxt_island/../../../../internal/service.json if path traversal is not properly handled by the server.
Impact Assessment
- Limited Impact: The vulnerability has a low severity due to the highly specific prerequisites
- No Direct Data Exfiltration: The vulnerability does not directly expose sensitive data
- Client-Side Only: Requests originate from the client, not the server
Mitigation
Action Required:
- Update to Nuxt 3.19.0+ or 4.1.0+ immediately
- Review any prerendered pages that fetch external or user-controlled data
Temporary Workarounds (if immediate update is not possible):
- Disable prerendering for pages that fetch user-controlled data
- Implement strict input validation on API endpoints used during prerendering
- Use allowlists for API response structures during prerendering
Fix Details
The fix implemented validation for Island keys in revive-payload.server.ts:
- Island keys must match the pattern
/^[a-z][a-z\d-]*_[a-z\d]+$/i - Maximum length of 100 characters
- Prevents path traversal and special characters
Credited to apyatko.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-128071
Nuxt: Incomplete fix for GHSA-6gq8-jgmh-3ffp: an encoded slash (`%2F`) in the request path bypasses route rules on catch-all page routes
medium6.5No fixNov 16, 2026CVE-2026-128074
Nuxt payload URL generation has quadratic cost for repeated slashes in the request path
medium6.9Nov 16, 2026CVE-2026-128075
Nuxt exposes the message and data of unhandled errors thrown during server rendering
medium5.3No fixNov 16, 2026CVE-2026-128076
Nuxt: Colliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342)
low3.1No fixNov 16, 2026CVE-2026-119200
Nuxt: Dot segments in the request path bypass `server/middleware` path checks and server route rules on page routes
medium6.5Oct 30, 2026CVE-2026-114130
Nuxt: Incomplete fix for GHSA-934w-87qh-qr26: a `javascript:` URL prefixed with an ASCII control character executes from `<NuxtLink>` when `pages` is disabled
low2.3Oct 22, 2026
