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.
CVE-2026-49993
This medium-severity CVE scores 5.7 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.7
- EG Score
- 5.7(medium)
- EPSS
- 19.9%
- KEV
- Not listed
Published
June 12, 2026
Last Modified
June 15, 2026
Advisory Details (5)
Auto-updated Jun 13, 2026@nuxt/webpack-builder and @nuxt/rspack-builder dev server same-origin check bypassed when Sec-Fetch-Site, Origin, and Referer are all absent (incomplete fix for GHSA-6m52-m754-pw2g) · Advisory · nuxt/nuxt · GitHub
https://github.com/nuxt/nuxt/security/advisories/GHSA-x6qj-4h56-5rj5Dev server exposes built source over LAN to malicious sites (incomplete fix for GHSA-4gf7-ff8x-hq99) · Advisory · nuxt/nuxt · GitHub
https://github.com/nuxt/nuxt/security/advisories/GHSA-6m52-m754-pw2gfix(rspack,webpack): require loopback host when missing same-origin signals
Fix merged in nuxt/nuxt PR #35200 on 2026-05-28 — awaiting tagged release
https://github.com/nuxt/nuxt/pull/35200commit e351de943e82 (nuxt/nuxt)
Fix landed in nuxt/nuxt commit e351de943e82 — awaiting tagged release
https://github.com/nuxt/nuxt/commit/e351de943e82db16970618b60dc7fdbaa58630f3commit 77187ee4015e (nuxt/nuxt)
Fix landed in nuxt/nuxt commit 77187ee4015e — awaiting tagged release
https://github.com/nuxt/nuxt/commit/77187ee4015e9267fb464951542a3e09e8b5fa05Vendor Advisories for CVE-2026-49993(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 1 ecosystem)
npm(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| @nuxt/rspack-builder | — | 3.21.7 | — |
| @nuxt/webpack-builder | — | 3.21.7 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 59× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-07 01:16 UTCEG score recompute
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 10:47 UTCEG score recompute
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 11:01 UTCEG score recompute
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 07:35 UTCEG score recompute
- 2026-07-02 06:04 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 06:56 UTCEG score recompute
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 07:58 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 09:01 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 10:03 UTCEG score recompute
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 11:04 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 12:07 UTCEG score recompute
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 07:05 UTCEG score recompute
Show 34 moreShow fewer
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-24 07:48 UTCEG score recompute
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 08:09 UTCEG score recompute
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 06:30 UTCEG score recompute
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 07:27 UTCEG score recompute
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-20 08:01 UTCEG score recompute
- 2026-06-19 19:26 UTCEPSS rescore
- 2026-06-19 19:26 UTCEPSS rescore
- 2026-06-19 09:00 UTCEG score recompute
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 10:00 UTCEG score recompute
- 2026-06-17 11:02 UTCEG score recompute
- 2026-06-16 17:53 UTCEPSS rescore
- 2026-06-16 12:05 UTCEG score recompute▼ 0.20
- 2026-06-15 19:45 UTCNVD updateCVSS v3 → 5.7
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 13:05 UTCEG score recompute
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-14 14:08 UTCEG score recompute
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-13 15:10 UTCEG score recompute
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 16:12 UTCEG score recompute
- 2026-06-12 16:12 UTCNVD updatefirst tracked
Frequently asked(5)
What is CVE-2026-49993?
When was CVE-2026-49993 disclosed?
Is CVE-2026-49993 actively exploited?
What is the CVSS score of CVE-2026-49993?
How do I remediate CVE-2026-49993?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49993
Is Your Infrastructure Affected by CVE-2026-49993?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.