CVE-2026-106108: Quasar Framework App Vite SSG Page Output Vulnerability

MODERATE
Advisory Identifier: GHSA-vhhq-m2gm-rwc9
Share
CWE-22
Published
Advisory Summary

CVE-2026-106108 is a MODERATE app vite ssg page output vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting Quasar Framework libraries in the npm ecosystem. The issue involves app vite ssg page output paths can escape the configured distribution directory. Remediation is available by upgrading affected packages to version 3.3.0.

CVE-2026-106108 at a Glance

CVE Identifier CVE-2026-106108
GHSA Identifier GHSA-vhhq-m2gm-rwc9
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Affected Product Quasar Framework
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-106108

To remediate this vulnerability, upgrade all affected Quasar Framework dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@quasar/app-vite fixed: 3.3.0 
npm install @quasar/app-vite@3.3.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls @quasar/app-vite

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-106108, inspect your project dependencies using npm:

npm ls @quasar/app-vite

Analyze the terminal output to locate any version of Quasar Framework in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.3.0), your application is affected.

Note: The npm ls @quasar/app-vite command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. In Quasar Framework, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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.

CVE-2026-106108 Affected Quasar Framework Versions

1 component(s)
Fixed Versions:
3.3.0
Product / Package Ecosystem Affected Versions Fixed Version
@quasar/app-vite
npm/@quasar/app-vite
npm
≥ 3.1.0
< 3.3.0
3.3.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/quasarframework/quasar/security/advisories/GHSA-vhhq-m2gm-rwc9
Security Fix Commit FIX COMMIT
https://github.com/quasarframework/quasar/commit/cdd4daeec839215540221122763c7a17cd478abc
Quasar Framework Source Repository REPOSITORY
https://github.com/quasarframework/quasar
Quasar Framework Release RELEASE
https://github.com/quasarframework/quasar/releases/tag/@quasar/app-vite-v3.1.0

Frequently Asked Questions

What is CVE-2026-106108?
CVE-2026-106108 is a security vulnerability in Quasar Framework involving App Vite SSG page output paths can escape the configured distribution directory under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').
Which Quasar Framework versions are affected?
Affected versions include releases prior to 3.3.0 across affected packages: @quasar/app-vite.
What version fixes CVE-2026-106108?
Upgrading to 3.3.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @quasar/app-vite affected?
Yes, @quasar/app-vite is affected in releases prior to 3.3.0. Upgrade your dependency to 3.3.0 or later.
What CWE is associated with CVE-2026-106108?
CVE-2026-106108 is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.).
How can I check npm dependencies for CVE-2026-106108?
Run the dependency tree command: 'npm ls @quasar/app-vite'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-vhhq-m2gm-rwc9",
  "modified" : "2026-10-07T16:14:41Z",
  "published" : "2026-10-07T16:14:41Z",
  "aliases" : [ "CVE-2026-106108" ],
  "summary" : "Quasar Framework: App Vite SSG page output paths can escape the configured distribution directory",
  "details" : "## Summary\n\nDuring 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.\n\n## Details\n\nA 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.\n\nQuasar 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.\n\n## Impact\n\nAn attacker able to influence an application's SSG page definitions could create files outside the intended build output directory during `quasar build -m ssg`.\n\n## Remediation\n\nResolve 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.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:A/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@quasar/app-vite"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.1.0"
      }, {
        "fixed" : "3.3.0"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.2.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/quasarframework/quasar/security/advisories/GHSA-vhhq-m2gm-rwc9"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/quasarframework/quasar/commit/cdd4daeec839215540221122763c7a17cd478abc"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/quasarframework/quasar"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/quasarframework/quasar/releases/tag/@quasar/app-vite-v3.1.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-07T16:14:41Z",
    "nvd_published_at" : null
  }
}