Categories
CVE-2026-106109

Path Traversal in @quasar/app-vite (CVE-2026-106109)

Summary

Path traversal in @quasar/app-vite (CVE-2026-106109). Risk of unauthorized operations or information disclosure. Exploitable via build.distDir. Mitigation: upgrade to 3.3.0 or later.

Original description

The description as published by the source.

Summary

@quasar/app-vite recursively removes build.distDir before producing build artifacts. The configured path was made absolute, but it was not checked before removal. A configuration mistake could therefore target the project root, user home directory, a filesystem root, or another directory outside the project.

Details

The build command and mode builders passed the resolved output directory directly to fs-extra recursive removal. Existing symlink ancestors were not resolved before deletion either, so a path that appeared to be inside the project could operate on a directory outside it.

quasar.config is trusted application code, and no attacker-controlled input reaches build.distDir by default. This issue is primarily destructive-build safety hardening. It can become a security boundary when build configuration is generated or influenced by less-trusted automation.

Impact

Running a normal Quasar build with an unsafe build.distDir can delete data accessible to the build user before compilation begins.

Remediation

Validate the effective deletion target before every artifact cleanup. Always reject filesystem roots, the user home directory and the project root; resolve existing symlink ancestors; require an explicit build.allowOutsideProjectDistDir opt-in for external output directories; and log the exact resolved target before removal.

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-106109 has been found in @quasar/app-vite.
Attackers can target a specific entry point like build.distDir over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @quasar/app-vite to 3.3.0 or later.
If unsure, ask your IT team or search "@quasar/app-vite CVE-2026-106109" on the vendor's site.

CVE-2026-106109 (@quasar/app-vite) — CWE-22
Attack surface: build.distDir / quasar.config / build.allowOutsideProjectDistDir
Patched: 3.3.0 — 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 @quasar/app-vite. Attackers reach the vulnerable code path via build.distDir.

📍 Affected scope

Check the vendor advisory for the affected versions of @quasar/app-vite. Attack surface: build.distDir / quasar.config / build.allowOutsideProjectDistDir.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.3.0.

🛡️ 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 '@quasar/app-vite' . 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 '@quasar/app-vite' . | grep -v node_modules

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

  2. 2
    Apply patch patch
    Upgrade @quasar/app-vite to 3.3.0

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

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

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

Affected packages

npm @quasar/app-vite
[{"type":"SEMVER","events":[{"introduced":"1.0.0"},{"fixed":"3.3.0"}]}]

References

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