CVE-2026-106109: Quasar Framework: App Vite build cleanup can recursively remove unsafe configured output directories
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.
Published Oct 7, 2026
Affected packages
@quasar/app-vite
- Ecosystem
- npm
- Affected
- >= 1.0.0, <= 3.2.0
- Fixed in
- 3.3.0
- Check
npm ls @quasar/app-vite
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
Credited to hawkeye64.
References
- https://github.com/quasarframework/quasar/security/advisories/GHSA-q9mq-245r-4g93
- https://nvd.nist.gov/vuln/detail/CVE-2026-106109
- https://github.com/quasarframework/quasar/commit/6c009734b406e246a0855ed060e3a822de8aecc1
- https://github.com/quasarframework/quasar/releases/tag/@quasar/app-vite-v3.3.0
- https://github.com/advisories/GHSA-q9mq-245r-4g93
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-106105
Quasar Framework: Development TLS private keys are cached with overly permissive filesystem permissions
high8.4Oct 7, 2026CVE-2026-106106
Quasar Framework: SSR/SSG dev error page discloses the full shell environment and its </script> escape is bypassable
high7.1Oct 7, 2026CVE-2026-106107
Quasar Framework: App Vite SSR and SSG nonce attributes are not safely constrained
high8.3Oct 7, 2026CVE-2026-106108
Quasar Framework: App Vite SSG page output paths can escape the configured distribution directory
medium5.7Oct 7, 2026
