CVE-2025-24361
MEDIUMCVE-2025-24361 is a medium-severity (CVSS 5.3) CWE-749 vulnerability in @nuxt/webpack-builder. O3 Security confirms whether CVE-2025-24361 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Opening a malicious website while running a Nuxt dev server could allow read-only access to code
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
@nuxt/webpack-buildernpm@nuxt/rspack-buildernpmDescription
Nuxt is an open-source web development framework for Vue.js. Source code may be stolen during dev when using version 3.0.0 through 3.15.12 of the webpack builder or version 3.12.2 through 3.152 of the rspack builder and a victim opens a malicious web site. Because the request for classic script by a script tag is not subject to same origin policy, an attacker can inject a malicious script in their site and run the script. By using Function::toString against the values in window.webpackChunknuxt_app, the attacker can get the source code. Version 3.15.13 of Nuxt patches this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @nuxt/webpack-builder | ≥ 3.0.0&&< 3.15.3 | 3.15.3 |
| 📦npm | @nuxt/rspack-builder | ≥ 3.12.2&&< 3.15.3 | 3.15.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @nuxt/webpack-builder. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @nuxt/webpack-builder to 3.15.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-24361 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2025-24361 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2025-24361. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-24361 in your dependencies?
O3 detects CVE-2025-24361 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.