← Back
CVE-2026-45670
medium
CVSS 5.4
Vulnerability in @nuxt/rspack-builder (CVE-2026-45670)
Summary
vulnerability in @nuxt/rspack-builder (CVE-2026-45670). Risk of unauthorized operations or information disclosure. Exploitable via ``script.src``. Mitigation: upgrade to `4.4.6` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-45670** has been found in @nuxt/rspack-builder.
Attackers can target a specific entry point like ``script.src`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade @nuxt/rspack-builder to **4.4.6** or later.
If unsure, ask your IT team or search "@nuxt/rspack-builder CVE-2026-45670" on the vendor's site.
CVE-2026-45670 (@nuxt/rspack-builder) — CWE-749 / CVSS v3 5.4
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `script.src` / `Origin` / `Referer` / `Host`
Patched: `4.4.6` — 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/rspack-builder. Attackers reach the vulnerable code path via ``script.src`` without authentication.
📍 Affected scope
@nuxt/rspack-builder — . Attack surface: `script.src` / `Origin` / `Referer` / `Host`.
🔥 Severity
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **4.4.6**.
🛡️ 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/rspack-builder' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@nuxt/rspack-builder' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@nuxt/rspack-builder` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @nuxt/rspack-builder to 4.4.6ステージング環境で 4.4.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@nuxt/rspack-builder
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.6"}]}]
npm
@nuxt/webpack-builder
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.6"}]}]
References
- package https://github.com/nuxt/nuxt
- web https://github.com/nuxt/nuxt/security/advisories/GHSA-6m52-m754-pw2g
- web https://github.com/nuxt/nuxt/pull/35051
- web https://github.com/advisories/GHSA-6m52-m754-pw2g
- web https://github.com/nuxt/nuxt/security/advisories/GHSA-4gf7-ff8x-hq99
- web https://nvd.nist.gov/vuln/detail/CVE-2026-45670