cve.bz

CVE-2026-106108 Path traversal

5.7 mediumEPSS 0.1%Fix available

Medium (5.7). EPSS 0.1% estimated probability of exploitation activity in the next 30 days. Fixed in @quasar/app-vite 3.3.0.

On this page
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.

Severity

CVSS 4.0

5.7 medium
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
EPSS
0.1% (unchanged from 0.1% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 3rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • @quasar/app-vite (npm): fixed in 3.3.0

Ask an AI about this CVE

Show the promptExplain CVE-2026-106108 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-106108?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-106108?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-106108 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
quasarframework quasar>= 2.22.0, < 2.23.3
@quasar app-vite>= 3.1.0, < 3.3.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-vhhq-m2gm-rwc9npm@quasar/app-vite>=3.1.0 <3.3.03.3.0

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A moderate impact path traversal vulnerability was found in @quasar/app-vite, the Vite-based build tool of the Quasar Framework distributed as an npm package, affecting versions 3.1.0 through 3.2.0. During static site generation (SSG), page definitions returned by getSsgPages() could supply custom dir and filename values that were joined to the configured build output directory (build.distDir) without verifying that the final destination remained inside the distribution directory. An attacker able to influence an application's SSG page definitions, for example when a build process derives them from external or otherwise untrusted content, could use parent-directory traversal or an existing symlink below the distribution directory to create new files or directories outside the intended build output tree with the permissions of the build user. Quasar application configuration and SSG page definitions are trusted input by default, so this is not normally a remote file-write primitive, and existing files are protected by the SSG renderer's no-overwrite behavior; the impact is limited to integrity through the creation of new files at locations writable by the build user. Red Hat rates this flaw as moderate impact (CVSS 4.7), consistent with the moderate severity assigned by the upstream record. No Red Hat products are currently listed as affected by this flaw.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. For applications built with the upstream @quasar/app-vite npm package, this issue is addressed by upgrading to a version that contains the upstream fix (3.3.0 or later).

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-106108.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON