What is CVE-2025-24360?

CVE-2025-24360 is a medium-severity security vulnerability in @nuxt/vite-builder (npm), affecting versions >= 3.8.1, < 3.15.3. It is fixed in 3.15.3.

How severe is CVE-2025-24360?

CVE-2025-24360 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of @nuxt/vite-builder are affected by CVE-2025-24360?

@nuxt/vite-builder (npm) versions >= 3.8.1, < 3.15.3 is affected.

Is there a fix for CVE-2025-24360?

Yes. CVE-2025-24360 is fixed in 3.15.3. Upgrade to this version or later.

Is CVE-2025-24360 exploitable, and should I be worried?

Whether CVE-2025-24360 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-24360 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2025-24360 in @nuxt/vite-builder

Q: How severe is CVE-2025-24360?

CVE-2025-24360 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of @nuxt/vite-builder are affected by CVE-2025-24360?

@nuxt/vite-builder (npm) versions >= 3.8.1, < 3.15.3 is affected.

Q: Is there a fix for CVE-2025-24360?

Yes. CVE-2025-24360 is fixed in 3.15.3. Upgrade to this version or later.

Q: Is CVE-2025-24360 exploitable, and should I be worried?

Whether CVE-2025-24360 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-24360 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-24360?

Upgrade @nuxt/vite-builder to 3.15.3 or later.

Summary

Opening a malicious website while running a Nuxt dev server could allow read-only access to code

Nuxt allows any websites to send any requests to the development server and read the response due to default CORS settings.

Details

While Vite patched the default CORS settings to fix https://github.com/vitejs/vite/security/advisories/GHSA-vg6x-rcgg-rjx6, nuxt uses its own CORS handler by default (https://github.com/nuxt/nuxt/pull/23995).

https://github.com/nuxt/nuxt/blob/7d345c71462d90187fd09c96c7692f306c90def5/packages/vite/src/client.ts#L257-L263

That CORS handler sets Access-Control-Allow-Origin: *.

[!IMPORTANT]
If on an affected version, it may be possible to opt-out of the default Nuxt CORS handler by configuring vite.server.cors.

PoC

Start a dev server in any nuxt project using Vite by nuxt dev.
Send a fetch request to http://localhost:3000/_nuxt/app.vue (fetch('http://localhost:3000/_nuxt/app.vue')) from a different origin page.

Additional Information

/__nuxt_vite_node__/manifest / /__nuxt_vite_node__/module also seems to have Access-Control-Allow-Origin: *, so it maybe also possible to exploit that handler.
https://github.com/nuxt/nuxt/blob/7d345c71462d90187fd09c96c7692f306c90def5/packages/vite/src/vite-node.ts#L39
Although I didn't find a valid module id.
Note that this handler is probably also vulnerable to DNS rebinding attacks as I didn't find any host header checks.

Impact

Users with the default server.cors option using Vite builder may get the source code stolen by malicious websites

CVE-2025-24360 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.15.3); upgrading removes the vulnerable code path.

Affected versions

@nuxt/vite-builder (>= 3.8.1, < 3.15.3)

Security releases

@nuxt/vite-builder → 3.15.3 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade @nuxt/vite-builder to 3.15.3 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-24360? CVE-2025-24360 is a medium-severity security vulnerability in @nuxt/vite-builder (npm), affecting versions >= 3.8.1, < 3.15.3. It is fixed in 3.15.3.
How severe is CVE-2025-24360? CVE-2025-24360 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of @nuxt/vite-builder are affected by CVE-2025-24360? @nuxt/vite-builder (npm) versions >= 3.8.1, < 3.15.3 is affected.
Is there a fix for CVE-2025-24360? Yes. CVE-2025-24360 is fixed in 3.15.3. Upgrade to this version or later.
Is CVE-2025-24360 exploitable, and should I be worried? Whether CVE-2025-24360 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-24360 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-24360? Upgrade @nuxt/vite-builder to 3.15.3 or later.