NVD / CVE Program· CNA GitHub_M

CVE-2025-59414: Nuxt Client-Side Path Traversal in Nuxt Island Payload Revival

Noroxi assessment

Priority: Monitor (action score 12/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.36% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
Fixed version: nuxt (npm) 3.19.0, 4.1.0.

Low priority for now. Upgrade to nuxt (npm) 3.19.0, 4.1.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Nuxt is an open-source web development framework for Vue.js. Prior to 3.19.0 and 4.1.0, 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. 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. During prerendering, if an API endpoint returns user-controlled data containing a crafted __nuxt_island object, he data gets serialized with devalue.stringify and stored in the prerendered page. When a client navigates to the prerendered page, devalue.parse deserializes the payload. The Island reviver attempts to fetch /__nuxt_island/${key}.json where key could contain path traversal sequences. Update to Nuxt 3.19.0+ or 4.1.0+.

LowCVSS 3.1 · v3.1—No exploit Fix available

GHSA-p6jq-8vc4-79f6

Published: Sep 17, 2025
Updated: Jun 17, 2026
EPSS: 0.3% · 30th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 12 / 40 · 3.1 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 3.1
CNA · GitHub_M: 3.1; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
nuxt	nuxt	cpe:2.3:a:nuxt:nuxt

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

nuxt nuxt3.6.0 and later · before 3.19.0
nuxt nuxt4.0.0 and later · before 4.1.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

nuxt nuxt
- >= 3.6.0 < 3.19.0, >= 4.0.0 < 4.1.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
npm	nuxt	from 3.6.0 · before 3.19.0	3.19.0
npm	nuxt	from 4.0.0 · before 4.1.0	4.1.0

Same product

nuxt: all records

Other highest-scoring records for the same primary product.

CVE-2023-3224Code Injection in nuxt/nuxt
57Plan
CVE-2026-53721Nuxt: Route-rule middleware bypass via case-sensitivity mismatch between vue-router and the routeRules matcher
35Monitor
CVE-2024-34344Remote code execution via the browser when running the test locally in nuxt
35Monitor

Published before and after this one in the same product

← EarlierCVE-2025-24361Jan 24, 2025 · Opening a malicious website while running a Nuxt dev server could allow read-only access to code
21Monitor
← EarlierCVE-2025-27415Mar 19, 2025 · Nuxt allows DOS via cache poisoning with payload rendering response
30Monitor
Later →CVE-2026-45669Jun 12, 2026 · Nuxt: Reflected XSS in `navigateTo()` external redirect
21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
npm:nuxt	3.19.0	Package registry (OSV)
npm:nuxt	4.1.0	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

nuxt/nuxtcommit 2566d20

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2024-23657408 days apartPath Traversal: '../filedir' in Nuxt Devtools
35Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

VercelHackerOne · paid · nuxt/nuxt

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
A user must open a link or visit a page.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: low · data can be read
Integrity: none
Availability: none

Attack vector: Network
Attack complexity: High
Privileges required: None
User interaction: Required
Scope: Unchanged
Confidentiality impact: Low
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:45 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/nuxt/nuxt/commit/2566d2046bccb158d98fb13e42ce4b2c33fb2595

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records