Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-47428 critical CVSS 9.6

Cross-Site Scripting (XSS) in @vitest/browser (CVE-2026-47428)

Summary

cross-site scripting in @vitest/browser (CVE-2026-47428). Successful exploitation can lead to full system takeover. Exploitable via ``otelCarrier``. Mitigation: upgrade to `5.0.0-beta.3` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-47428** has been found in @vitest/browser. Attackers can target a specific entry point like ``otelCarrier`` over the network to misuse the product. Successful exploitation can lead to full system takeover. CVSS score: 9.6/10. What to do: upgrade @vitest/browser to **5.0.0-beta.3** or later. If unsure, ask your IT team or search "@vitest/browser CVE-2026-47428" on the vendor's site.
CVE-2026-47428 (@vitest/browser) — CWE-79 / CVSS v3 9.6 Attack vector: remote (network-reachable) / unauthenticated Attack surface: `otelCarrier` / `VITEST_API_TOKEN` / `vite.config.ts` / `window.VITEST_API_TOKEN` Patched: `5.0.0-beta.3` — 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
**Cross-site scripting (XSS)** (CWE-79) exists in @vitest/browser. Attackers reach the vulnerable code path via ``otelCarrier`` without authentication.
📍 Affected scope
@vitest/browser — . Attack surface: `otelCarrier` / `VITEST_API_TOKEN` / `vite.config.ts` / `window.VITEST_API_TOKEN`.
🔥 Severity
Severity: Critical (CVSS 9.6/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **5.0.0-beta.3**.
🛡️ 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 '@vitest/browser' .` 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

  1. 1
    Identify exposure identify 
    grep -r '@vitest/browser' . | grep -v node_modules

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

  2. 6
    Apply patch patch 
    Upgrade @vitest/browser to 5.0.0-beta.3

    ステージング環境で 5.0.0-beta.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

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

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

Affected packages

npm @vitest/browser
[{"type":"SEMVER","events":[{"introduced":"5.0.0-beta.0"},{"fixed":"5.0.0-beta.3"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →