Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3amended

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

CVE-2025-24361GHSA-4gf7-ff8x-hq99

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@nuxt/rspack-builder 3.15.3; @nuxt/webpack-builder 3.15.3), 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

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.3 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
EPSS
  • CVE-2025-24361: 0.34% estimated exploitation activity in the next 30 days; percentile 27.77 (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 Source code may be stolen during dev when using webpack / rspack builder and you open a malicious web site. Details Because the request for classic script by a script tag is not subject to same origin policy, an attacker can inject <script src="http://localhost:3000/nuxt/app.js" in their site and run the script. By using Function::toString against the values in window.webpackChunknuxtapp, the attacker can get the source code. PoC 1. Create a nuxt project with webpack / rspack builder. 1. Run npm run dev 1. Open http://localhost:3000 1. Run the script below in a web site that has a different origin. 1. You can see the source code output in the document and the devtools console. It contains the compiled source code and also the source map (but it seems the sourcemap contains transformed content in the sourcesContent field). Impact Users using webpack / rspack builder may get the source code stolen by malicious websites.

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

    Amended from ghsa record GHSA-4gf7-ff8x-hq99

  2. Revision 1 · created ·

    Published from osv record GHSA-4gf7-ff8x-hq99

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-24361

Advisory: Opening a malicious website while running a Nuxt dev server could allow read-only access to code
IDs: CVE-2025-24361, GHSA-4gf7-ff8x-hq99
Record: https://patchnext.com/advisories/cve-2025-24361 (revision 2, source checked 26 Oct 2026, 12:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @nuxt/rspack-builder 3.15.3; @nuxt/webpack-builder 3.15.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @nuxt/rspack-builder: affected >= 3.12.2, < 3.15.3; fixed in 3.15.3
- npm @nuxt/webpack-builder: affected >= 3.0.0, < 3.15.3; fixed in 3.15.3

## Suggested inspection (read-only)
- `npm ls @nuxt/rspack-builder --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @nuxt/webpack-builder --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/rspack-builder, @nuxt/webpack-builder.
- 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-4gf7-ff8x-hq99 (OSV record GHSA-4gf7-ff8x-hq99 lists affected ranges: npm @nuxt/webpack-builder >=3.0.0 =3.12.2 <3.15.3 (fixed))
- Verified: https://github.com/advisories/GHSA-4gf7-ff8x-hq99 (GitHub-reviewed advisory GHSA-4gf7-ff8x-hq99 lists affected ranges: npm @nuxt/webpack-builder >=3.0.0 =3.12.2 <3.15.3)

Commands are suggestions: review each one before running it.

Loading voting…