Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 3.1amended

Nuxt has Client-Side Path Traversal in Nuxt Island Payload Revival

CVE-2025-59414GHSA-p6jq-8vc4-79f6

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (nuxt 4.1.0, 3.19.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm nuxt

    Affected
    >= 3.6.0, < 3.19.0>= 4.0.0, < 4.1.0
    Fixed in
    3.19.0, 4.1.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
3.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
EPSS
  • CVE-2025-59414: 0.37% estimated exploitation activity in the next 30 days; percentile 30.82 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 nuxtisland objects. The issue affects the following flow: 1. During prerendering, if an API endpoint returns user-controlled data containing a crafted nuxtisland object 2. This data gets serialized with devalue.stringify and stored in the prerendered page 3. When a client navigates to the prerendered page, devalue.parse deserializes the payload 4. The Island reviver attempts to fetch /nuxtisland/${key}.json where key could contain path traversal sequences Prerequisites for Exploitation This vulnerability requires all of the following conditions: 1.…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-p6jq-8vc4-79f6

  2. Revision 1 · created ·

    Published from osv record GHSA-p6jq-8vc4-79f6

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-59414

Advisory: Nuxt has Client-Side Path Traversal in Nuxt Island Payload Revival
IDs: CVE-2025-59414, GHSA-p6jq-8vc4-79f6
Record: https://patchnext.com/advisories/cve-2025-59414 (revision 2, source checked 26 Oct 2026, 12:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nuxt 4.1.0, 3.19.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nuxt: affected >= 3.6.0, < 3.19.0; >= 4.0.0, < 4.1.0; fixed in 3.19.0, 4.1.0

## Suggested inspection (read-only)
- `npm ls nuxt --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nuxt.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-p6jq-8vc4-79f6 (OSV record GHSA-p6jq-8vc4-79f6 lists affected ranges: npm nuxt >=3.6.0 =4.0.0 <4.1.0 (fixed))
- Verified: https://github.com/advisories/GHSA-p6jq-8vc4-79f6 (GitHub-reviewed advisory GHSA-p6jq-8vc4-79f6 lists affected ranges: npm nuxt >=3.6.0 =4.0.0 <4.1.0)

Commands are suggestions: review each one before running it.

Loading voting…