dbcve.org
Nuxt\/rspack BuilderApplication · Nuxt

CVE-2026-49993

MEDIUM · 5.7 CVSS v3.1 Published 2026-06-12
Fix available
A fix is available. Upgrade to 3.21.7 / 4.4.7 or later.
See remediation →
60/100
Remediation priority · Elevated
Public exploit No privileges Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Nuxt is an open-source web development framework for Vue.js. In @nuxt/rspack-builder and @nuxt/webpack-builder from versions 3.15.4 to before 3.21.7 and 4.0.0 to before 4.4.7, there is an incomplete fix for GHSA-6m52-m754-pw2g. Source code may still be stolen during dev when using the webpack / rspack builder if the dev server is bound to a non-loopback address (e.g. nuxt dev --host) and the developer opens a malicious site on the same network. This issue has been patched in versions 3.21.7 and 4.4.7.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Nuxt\/rspack BuilderApplication
Affected:>= 3.15.4, < 3.21.7>= 4.0.0, < 4.4.7
Nuxt\/webpack BuilderApplication
Affected:>= 3.15.4, < 3.21.7>= 4.0.0, < 4.4.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.21.7 / 4.4.7 or later
Fixed in 3.21.74.4.7
Vendor patch github.com →
Recommended fix High confidence

Nuxt 3.x: upgrade to 3.21.7 or later; Nuxt 4.x: upgrade to 4.4.7 or later

  1. Check current Nuxt version by examining package.json or running npm list nuxt
  2. For Nuxt 3.x users: upgrade to version 3.21.7 or later by running: npm install nuxt@^3.21.7 or yarn add nuxt@^3.21.7
  3. For Nuxt 4.x users: upgrade to version 4.4.7 or later by running: npm install nuxt@^4.4.7 or yarn add nuxt@^4.4.7
  4. After upgrade, verify the fix by reviewing the commit at https://github.com/nuxt/nuxt/commit/77187ee4015e9267fb464951542a3e09e8b5fa05 to confirm the security patch is applied
  5. Test the dev server behavior when binding to non-loopback addresses to ensure source code is no longer exposed
Caveat Major version upgrades (3.x to 4.x) may introduce breaking changes; review Nuxt 4 migration guide before upgrading across major versions

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-49993 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-49993 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data