Skip to main content
VulnerabilityPublished

CVE-2026-106109: quasarframework quasar · Path Traversal

Affects quasarframework quasarSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.1 Medium : upgrade to 2.23.3 when convenient.

Data as of 20 Nov 2026, 17:34 UTC

CVSS 4.0 base score
4.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.23.3, 3.3.0
CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade quasar to 2.23.3; app-vite to 3.3.0.

Affected software

ProductAffectedFixed in
quasarframeworkquasarAffected
  • >=2.7.0 <2.23.3
Fixed in
  • 2.23.3
@quasarapp-viteAffected
  • >=1.0.0 <3.3.0
Fixed in
  • 3.3.0

AI-suggested

Upgrade to Quasar Framework version 3.3.0 or later, where this issue is fixed. Until then, ensure that build configurations do not set build.distDir to critical directories such as the project root, user home, filesystem roots, or symlink-resolved external directories. Avoid running builds with untrusted or compromised automation that could influence the build configuration. Patch status is confirmed fixed in version 3.3.0.

Description

CVE-2026-106109 is a path traversal vulnerability in the Quasar Framework's @quasar/app-vite build tool. Versions from 1.0.0 up to but not including 3.3.0 recursively remove the resolved build.distDir directory before building without properly restricting critical directories such as the project root, user home, filesystem roots, or symlink-resolved external directories. This can lead to unintended deletion of data writable by the build user if an unsafe trusted configuration is used. Exploitation requires either compromised or less-trusted automation influencing the build configuration or a developer running a mistaken configuration. The vulnerability is fixed in version 3.3.0.

References

Community reviews

Loading reviews…