Summary
Quasar Framework: App Vite SSG page output paths can escape the configured distribution directory
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.
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
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.
Frequently Asked Questions
- What is CVE-2026-106108? CVE-2026-106108 is a medium-severity path traversal vulnerability in @quasar/app-vite (npm), affecting versions >= 3.1.0, <= 3.2.0. It is fixed in 3.3.0. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- Which versions of @quasar/app-vite are affected by CVE-2026-106108? @quasar/app-vite (npm) versions >= 3.1.0, <= 3.2.0 is affected.
- Is there a fix for CVE-2026-106108? Yes. CVE-2026-106108 is fixed in 3.3.0. Upgrade to this version or later.
- Is CVE-2026-106108 exploitable, and should I be worried? Whether CVE-2026-106108 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-106108 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-106108? Upgrade
@quasar/app-viteto 3.3.0 or later.