Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-106108 Overview
CVE-2026-106108 is a path traversal vulnerability [CWE-22] in the Quasar Framework's @quasar/app-vite package. The flaw affects static site generation (SSG) page definitions returned by getSsgPages(). The dir and filename values are joined to build.distDir without validating the final destination path. Parent directory traversal sequences or pre-existing symlinks beneath the distribution directory can create HTML files or directories outside the intended output tree, running with the build user's permissions. The vulnerability affects versions from 3.1.0 through 3.3.0 and is fixed in version 3.3.0.
Critical Impact
Exploitation requires a build pipeline that derives SSG page definitions from untrusted content, but a successful attack writes attacker-controlled HTML files outside the distribution directory with the privileges of the build process.
Affected Products
- @quasar/app-vite version 3.1.0
- @quasar/app-vite versions above 3.1.0 and below 3.3.0
- Quasar Framework SSG build workflows using getSsgPages()
Discovery Timeline
- 2026-10-13 - CVE CVE-2026-106108 published to NVD
- 2026-10-13 - Last updated in NVD database
- Version 3.3.0 - Quasar releases @quasar/app-vite v3.3.0 containing the fix
Technical Details for CVE-2026-106108
Vulnerability Analysis
The vulnerability resides in the SSG builder of @quasar/app-vite. During static site generation, getSsgPages() returns page definitions containing dir and filename fields. The builder joins these values with the configured build.distDir to produce output paths. The join operation does not confirm that the resulting path remains within distDir.
Attackers who influence SSG page definitions can supply values containing .. segments or point to symbolic links placed under distDir. The builder then writes generated HTML content to arbitrary file system locations writable by the build user. Existing files on disk remain protected because the renderer refuses to overwrite them, limiting the primitive to file and directory creation rather than modification.
Exploitation requires a non-default build configuration. Quasar treats application configuration and SSG page definitions as trusted inputs, so the vulnerability is only reachable when the build pipeline derives these values from external content such as content management systems, markdown repositories, or user-submitted data.
Root Cause
The ssg-builder.js module performed path concatenation without a containment check. There was no verification that the resolved absolute path remained a descendant of build.distDir, and no handling for symbolic links encountered during traversal.
Attack Vector
The attack vector is local. An attacker must be able to influence the SSG page definitions consumed by the Quasar build process. This typically requires write access to a data source used by the build pipeline, such as a content repository or CMS feed, combined with user interaction in the form of initiating or scheduling a build.
// Patch excerpt: new containment helper introduced in the fix
// Source: app-vite/lib/utils/get-contained-file-path.js
import fse from 'fs-extra'
import { dirname, isAbsolute, relative, resolve, sep } from 'node:path'
function isContainedPath(root, target, allowRoot) {
const relativePath = relative(root, target)
return (
(allowRoot === true || relativePath !== '') &&
relativePath !== '..' &&
relativePath.startsWith(`..${sep}`) === false &&
isAbsolute(relativePath) === false
)
}
async function getExistingAncestor(target) {
let current = target
while (true) {
try {
await fse.lstat(current)
return current
} catch (err) {
if (err.code !== 'ENOENT' && err.code !== 'ENOTDIR') {
throw err
}
}
const parent = dirname(current)
if (parent === current) {
// traversal terminates at filesystem root
}
}
}
Source: GitHub Commit cdd4dae
Detection Methods for CVE-2026-106108
Indicators of Compromise
- HTML files or directories created outside the configured build.distDir after an SSG build completes.
- SSG page definitions containing .. sequences, absolute paths, or references that resolve through symlinks.
- Unexpected symbolic links placed inside the distribution directory prior to build execution.
Detection Strategies
- Audit CI/CD build logs for file write operations outside the project's declared output directory.
- Scan content sources that feed getSsgPages() for dir or filename fields containing traversal characters.
- Compare the post-build filesystem state against an expected manifest of files under distDir.
Monitoring Recommendations
- Enable filesystem auditing on build agents to log file creation events outside project workspaces.
- Alert on symlink creation inside directories designated as SSG output targets.
- Track @quasar/app-vite package versions across projects and flag any installation between 3.1.0 and 3.3.0.
How to Mitigate CVE-2026-106108
Immediate Actions Required
- Upgrade @quasar/app-vite to version 3.3.0 or later in all projects.
- Review build pipelines that generate SSG page definitions from external content and validate dir and filename values before use.
- Remove unexpected symbolic links from the build.distDir tree before invoking the build.
Patch Information
The fix is included in @quasar/app-vite v3.3.0. The patch introduces a getContainedFilePath() helper that resolves each target path, walks existing ancestors to detect symlinks, and rejects any destination that falls outside distDir. See the GitHub Security Advisory GHSA-vhhq-m2gm-rwc9, the Quasar Release v3.3.0, and the patch commit cdd4dae for details.
Workarounds
- Treat quasar.config and SSG page definitions as code and avoid deriving them from untrusted content until the upgrade is applied.
- Sanitize dir and filename fields by rejecting values containing .., absolute paths, or null bytes before passing them to the SSG builder.
- Run builds in ephemeral containers with filesystem write access restricted to the project workspace.
# Upgrade @quasar/app-vite to the patched release
npm install @quasar/app-vite@^3.3.0
# Verify installed version
npm ls @quasar/app-vite
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

