CVE-2026-106108: Quasar Framework: App Vite SSG page output paths can escape the configured distribution directory
Summary During an SSG build, page definitions returned by getSsgPages() can provide custom dir and filename values. The builder joined those values to build.distDir and wrote the generated page without verifying that the final destination remained inside the distribution directory. Details A page definition containing parent-directory traversal could cause the build to create a new HTML file outside build.distDir.
Published Oct 7, 2026
Affected packages
@quasar/app-vite
- Ecosystem
- npm
- Affected
- >= 3.1.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
During an SSG build, page definitions returned by getSsgPages() can provide custom dir and filename values. The builder joined those values to build.distDir and wrote the generated page without verifying that the final destination remained inside the distribution directory.
Details
A page definition containing parent-directory traversal could cause the build to create a new HTML file outside build.distDir. An existing symlink below the distribution directory could also redirect a generated file or newly created directories outside the output tree.
Quasar application configuration and SSG page definitions are trusted input by default, so this is not normally a remote file-write primitive. The issue becomes relevant when an application derives SSG page definitions from external or otherwise untrusted content, or when build configuration is compromised. Existing files are protected by the SSG renderer's no-overwrite behavior, but new files and directories can be created with the permissions of the build user.
Impact
An attacker able to influence an application's SSG page definitions could create files outside the intended build output directory during quasar build -m ssg.
Remediation
Resolve each page destination against the real build.distDir, reject absolute and parent-traversing paths, reject destinations that resolve to the output root where a file is expected, and verify existing ancestors after resolving symlinks.
Credited to hawkeye64.
References
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-106109
Quasar Framework: App Vite build cleanup can recursively remove unsafe configured output directories
medium4.1Oct 7, 2026
