Quick answers
- Is CVE-2026-106108 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106108 being exploited in the wild.
- How severe is CVE-2026-106108?
- Medium severity, with a CVSS score of 4, published 13 October 2026.
- Which products and versions are affected?
- @quasar/app-vite (npm) >= 3.1.0, <= 3.2.0, SEMVER:introduced=3.1.0,fixed=3.3.0; Quasar Framework App Vite 3.1.0 through 3.2.0.
- Is there a fix for CVE-2026-106108?
- Yes. @quasar/app-vite (npm): upgrade to 3.3.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-106108 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-106108?
- Check whether you run @quasar/app-vite (npm) or Quasar Framework App Vite at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @quasar/app-vite (npm): upgrade to 3.3.0 or later
npm install @quasar/app-vite@3.3.0
Technical details
The vulnerability is a path traversal flaw (CWE-22) in the SSG build process where page definitions provide custom `dir` and `filename` values. The builder fails to validate that resolved paths remain within `build.distDir`, allowing parent-directory traversal sequences (e.g., `../`) and symlink-based redirection to escape the output tree. Exploitation requires the ability to influence SSG page definitions, which becomes practical when external or untrusted content feeds into configuration.
Affected products
- Quasar Framework App Vite 3.1.0 through 3.2.0
Identifiers
- CVE-2026-106108
- GHSA-vhhq-m2gm-rwc9
Timeline
- 2026-07-29: disclosed
- 2026-10-07: advisory