← Back
CVE-2026-47429
critical
CVSS 9.8
Path Traversal in vitest (CVE-2026-47429)
Summary
path traversal in vitest (CVE-2026-47429). Successful exploitation can lead to full system takeover. Exploitable via ``api.host``. Mitigation: upgrade to `3.2.6` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-47429** has been found in vitest.
Attackers can target a specific entry point like ``api.host`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade vitest to **3.2.6** or later.
If unsure, ask your IT team or search "vitest CVE-2026-47429" on the vendor's site.
CVE-2026-47429 (vitest) — CWE-22 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `api.host` / `isFileServingAllowed` / `cleanUrl` / `saveTestFile`
Patched: `3.2.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
**Path traversal** (CWE-22) exists in vitest. Attackers reach the vulnerable code path via ``api.host`` without authentication.
📍 Affected scope
vitest — . Attack surface: `api.host` / `isFileServingAllowed` / `cleanUrl` / `saveTestFile`.
🔥 Severity
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **3.2.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 'vitest' .` 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 'vitest' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `vitest` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade vitest to 3.2.6ステージング環境で 3.2.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
vitest
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.6"}]}]
References
- package https://github.com/vitest-dev/vitest
- web https://github.com/vitest-dev/vitest/security/advisories/GHSA-5xrq-8626-4rwp
- web https://github.com/vitest-dev/vitest/blob/eb1abf08573032a532015b999ad3501c5e89e3bb/packages/browser/src/node/commands/fs.ts#L10-L11
- web https://github.com/vitest-dev/vitest/blob/eb1abf08573032a532015b999ad3501c5e89e3bb/packages/browser/src/node/plugin.ts#L194-L196
- web https://github.com/vitest-dev/vitest/blob/eb1abf08573032a532015b999ad3501c5e89e3bb/packages/browser/src/node/rpc.ts#L115-L121
- web https://github.com/vitest-dev/vitest/blob/eb1abf08573032a532015b999ad3501c5e89e3bb/packages/ui/node/index.ts#L77
- web https://github.com/vitest-dev/vitest/blob/eb1abf08573032a532015b999ad3501c5e89e3bb/packages/vitest/src/api/setup.ts#L103-L105
- web https://github.com/vitest-dev/vitest/blob/eb1abf08573032a532015b999ad3501c5e89e3bb/packages/vitest/src/api/setup.ts#L119-L121
- web https://github.com/advisories/GHSA-5xrq-8626-4rwp
- web https://github.com/vitest-dev/vitest/commit/20e00ef7808de6d330c5e2fda530f686e08f1c8d
- web https://github.com/vitest-dev/vitest/commit/af88b1f5d82844a4761ea9a977156c98e2b14ca8
- web https://github.com/vitest-dev/vitest/pull/10445
- web https://github.com/vitest-dev/vitest/pull/9350
- web https://github.com/vitest-dev/vitest/releases/tag/v3.2.5
- web https://github.com/vitest-dev/vitest/releases/tag/v4.1.0
- web https://nvd.nist.gov/vuln/detail/CVE-2026-47429