Skip to main content
Vulnerability Database/CVE-2026-106109

CVE-2026-106109: Quasar Framework Path Traversal Vulnerability

CVE-2026-106109 is a path traversal vulnerability in Quasar Framework that allows unsafe directory deletion through build configuration. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-106109 Overview

CVE-2026-106109 affects the Quasar Framework, a Vue.js-based framework for building high-performance user interfaces. The @quasar/app-vite package recursively removed the resolved build.distDir before building, without rejecting the project root, user home directory, filesystem roots, or symlink-resolved external directories. A trusted but unsafe configuration could delete data writable by the build user before compilation starts. The flaw is tracked as a path traversal issue [CWE-22] and is fixed in version 3.3.0.

Critical Impact

An unsafe build.distDir value causes recursive deletion of arbitrary directories writable by the build user, including the project root or home directory.

Affected Products

  • @quasar/app-vite from 1.0.0 up to (but not including) 3.3.0
  • Quasar Framework projects using the Vite-based build pipeline
  • CI/CD pipelines where build configuration can be influenced by less-trusted automation

Discovery Timeline

  • 2026-10-06 - CVE-2026-106109 published to NVD
  • 2026-10-06 - Last updated in NVD database
  • Fix released - @quasar/app-vite v3.3.0 published on GitHub (Release Tag)

Technical Details for CVE-2026-106109

Vulnerability Analysis

The vulnerability resides in the Quasar build command for the Vite integration. Before compilation, @quasar/app-vite invoked fse.removeSync(outputFolder) on the resolved build.distDir path. The removal routine did not validate the resolved target against the project root, user home directory, filesystem roots, or symlink-resolved locations outside the project.

If build.distDir was configured, directly or through automation, to a path such as /, ~, or a symlink pointing outside the project, the build process recursively deleted every file writable by the build user at that location. The issue is classified as a path traversal weakness [CWE-22].

No attacker-controlled input reaches build.distDir by default. Exploitation requires a compromised build pipeline, a malicious dependency able to influence configuration, or a developer error that supplies an unsafe path.

Root Cause

The build routine trusted the configured output directory without boundary checks. The removeSync call followed symlinks and operated with the build user's privileges. There was no allow-list, no project-root containment check, and no opt-in flag for destinations outside the project tree.

Attack Vector

The vector is local and requires authored access to the Quasar configuration or build environment. A malicious contributor, compromised CI job, or supply-chain actor who can modify quasar.config or inject configuration overrides can set build.distDir to a sensitive directory. When the build runs, the pre-build cleanup step deletes the contents of that directory.

javascript
// Patch excerpt: packages/app-vite/lib/cmd/build.js
 const appBuilder = new QuasarModeBuilder({ argv, quasarConf })

-const { default: fse } = await import('fs-extra')
 let outputFolder = quasarConf.build.distDir
-fse.removeSync(outputFolder)
+const { removeBuildArtifacts } =
+  await import('../utils/remove-build-artifacts.js')
+try {
+  removeBuildArtifacts({
+    targetDir: outputFolder,
+    projectDir: ctx.appPaths.appDir,
+    allowOutsideProject: quasarConf.build.allowOutsideProjectDistDir
+  })
+} catch (err) {
+  fatal(err.message, 'FAIL')
+}

Source: Quasar commit 6c00973. The patch replaces the unchecked fse.removeSync with removeBuildArtifacts, which validates targetDir against projectDir and requires an explicit allowOutsideProjectDistDir opt-in.

Detection Methods for CVE-2026-106109

Indicators of Compromise

  • Unexpected deletion of files in developer home directories, project parents, or shared build volumes shortly after a quasar build invocation.
  • quasar.config or environment overrides setting build.distDir to an absolute path outside the project tree, a filesystem root, or a symlinked location.
  • Build logs showing a long pre-build cleanup phase or missing files immediately before Vite compilation starts.

Detection Strategies

  • Audit all repositories using @quasar/app-vite for build.distDir values that resolve outside the project directory or follow symlinks.
  • Scan CI/CD history for changes to Quasar configuration files, environment variables, or build scripts that modify distDir.
  • Compare installed @quasar/app-vite versions across projects and flag any below 3.3.0.

Monitoring Recommendations

  • Enable filesystem auditing on CI build agents for recursive unlink operations originating from Node.js build processes.
  • Alert on build jobs that delete files outside the designated workspace directory.
  • Track dependency updates for @quasar/app-vite across repositories using software composition analysis.

How to Mitigate CVE-2026-106109

Immediate Actions Required

  • Upgrade @quasar/app-vite to version 3.3.0 or later in every affected project.
  • Review quasar.config and CI environment variables for any build.distDir value that resolves outside the project root.
  • Restrict write permissions of the build user to the project workspace and designated artifact locations.
  • Treat build configuration files as security-sensitive and require code review before merging changes.

Patch Information

The fix is included in @quasar/app-vite v3.3.0. See the GitHub Security Advisory GHSA-q9mq-245r-4g93 and the release notes. The patch introduces removeBuildArtifacts, which rejects deletions targeting the project root, user home, filesystem roots, and symlink-resolved external directories unless build.allowOutsideProjectDistDir is explicitly set.

Workarounds

  • Pin build.distDir to a path strictly inside the project directory, such as dist/spa.
  • Run builds in ephemeral containers or sandboxes where the build user cannot write outside the workspace.
  • Avoid using symlinks inside the build output path and refuse pull requests that modify build.distDir.
bash
# Safe quasar.config excerpt
# build.distDir must remain inside the project directory
build: {
  distDir: 'dist/spa'
  # Do NOT set build.allowOutsideProjectDistDir unless strictly required
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.