CVE-2026-106108: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in quasarframework quasar
Description
CVE-2026-106108 is a path traversal vulnerability in the Quasar Framework's @quasar/app-vite SSG page definitions. Versions from 3.1.0 up to but not including 3.3.0 allow crafted dir and filename values to escape the intended build distribution directory, potentially creating files or directories outside the output tree with the build user's permissions. Exploitation requires that the build process uses untrusted external content for configuration or page definitions. The issue is fixed in version 3.3.0.
CVSS v4.0
Score 5.7medium
Affected software
quasarframework
quasar
@quasar
app-vite
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises because the getSsgPages() function in @quasar/app-vite returns page definitions with dir and filename values that are joined to the build.distDir path without verifying that the final resolved path remains within the intended directory. This improper limitation of pathname allows parent directory traversal or symlink exploitation to write files outside the designated output directory during the build process. Since application configuration and SSG page definitions are trusted by default, exploitation requires the build to incorporate external or less-trusted content. The renderer's no-overwrite behavior protects existing files, limiting some impact. The vulnerability affects Quasar Framework versions >=2.22.0 <2.23.3 and >=3.1.0 <3.3.0 and is resolved in 3.3.0.
Potential Impact
An attacker who can influence the build process with external or less-trusted content may cause the build to write new HTML files or directories outside the intended distribution directory. These files are created with the build user's permissions. Existing files are protected from overwrite by the renderer. This could lead to unauthorized file creation outside the expected output tree, potentially impacting system integrity depending on the build environment and permissions.
Mitigation Recommendations
Upgrade to Quasar Framework version 3.3.0 or later, where this vulnerability is fixed. Since this is a build-time vulnerability, ensure that all inputs to the build process, especially application configuration and SSG page definitions, are from trusted sources. No other vendor advisory or patch links are provided, so check the official Quasar Framework release notes for confirmation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-10-06T15:33:55.333Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ace48662cdf04f6567a47d8
Added to database: 10/13/2026, 15:04:06 UTC
Last enriched: 10/13/2026, 15:18:41 UTC
Last updated: 10/13/2026, 15:19:14 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.