Categories
CVE-2026-49993 medium CVSS 5.7

Vulnerability in @nuxt/webpack-builder (CVE-2026-49993)

Summary

Vulnerability in @nuxt/webpack-builder (CVE-2026-49993). Confidential information can be exposed externally. Exploitable via Origin. Mitigation: upgrade to 3.21.7 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-49993 has been found in @nuxt/webpack-builder.
Attackers can target a specific entry point like Origin over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.7/10.
What to do: upgrade @nuxt/webpack-builder to 3.21.7 or later.
If unsure, ask your IT team or search "@nuxt/webpack-builder CVE-2026-49993" on the vendor's site.

CVE-2026-49993 (@nuxt/webpack-builder) — CWE-749 / CVSS v3 5.7
Attack vector: adjacent-network / unauthenticated
Attack surface: Origin / Referer / crossorigin / e351de94
Patched: 3.21.7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-749) exists in @nuxt/webpack-builder. Attackers reach the vulnerable code path via Origin without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of @nuxt/webpack-builder. Attack surface: Origin / Referer / crossorigin / e351de94.

🔥 Severity

Severity: Medium (CVSS 5.7/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 3.21.7.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@nuxt/webpack-builder' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r '@nuxt/webpack-builder' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @nuxt/webpack-builder を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade @nuxt/webpack-builder to 3.21.7

    ステージング環境で 3.21.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @nuxt/webpack-builder
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.21.7"}]}]
npm @nuxt/rspack-builder
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.21.7"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details