Answer in brief
CVE-2026-106108 records a Medium severity (CVSS 5.7) vulnerability in Quasar Framework: App Vite SSG page output paths can escape the configured distribution directory. The current sources do not mark it as known exploited. The current feed maps @quasar/app-vite (generic), quasarframework/quasar (generic), @quasar/app-vite (npm). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps @quasar/app-vite (generic), quasarframework/quasar (generic), @quasar/app-vite (npm). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| @quasar/app-vitegeneric | >=3.1.0 <3.3.0 | 3.3.0 |
| quasarframework/quasargeneric | >=2.22.0 <2.23.3 | 2.23.3 |
| @quasar/app-vitenpm | >=3.1.0,<=3.2.0 | 3.3.0 |
Published upstream
Oct 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 7, 2026
Quasar Framework is a framework for building high-performance Vue.js user interfaces. From 3.1.0 until 3.3.0, @quasar/app-vite SSG page definitions returned by getSsgPages() could supply dir and filename values that were joined to build.distDir without verifying the final destination. Parent traversal or an existing symlink below the distribution directory could create new HTML files or directories outside the output tree with the build user's permissions. Application configuration and SSG page definitions are trusted by default, so exploitation requires a build process that derives them from external or otherwise less-trusted content; existing files remain protected by the renderer's no-overwrite behavior. This issue is fixed in version 3.3.0.
Quoted source text, attributed separately from HOL analysis.