Quasar Framework is a framework for building high-performance Vue.js user interfaces. From 1.0.0 until 3.3.0, @quasar/app-vite recursively removed the resolved build.distDir before building without rejecting the project root, user home directory, filesystem roots, or symlink-resolved external directories. An unsafe trusted configuration can delete data writable by the build user before compilation begins. No attacker-controlled input reaches build.distDir by default, so exploitation requires compromised or less-trusted automation to influence build configuration, or a developer to run a mistaken configuration. This issue is fixed in version 3.3.0.
CVE-2026-106109
MEDIUMPre-NVD 4.14.1
EchelonGraph scoreLOW confidence
This medium-severity CVE scores 4.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: secondary
4.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 4.1Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 4.1
- EG Score
- 4.1MEDIUMlow confidence
- EG Risk
- 18EG Risk 18/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity41% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at every mission impact level.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
CISA SSVCTrack at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 6, 2026
Last Modified
October 6, 2026
Advisory Details (2)
Auto-updated Oct 6, 2026Patch available. Sources: github, github_commit.
github_commit Patch Available
commit 6c009734b406 (quasarframework/quasar)
Patch available: quasarframework/quasar quasar-v2.26.0 (contains commit 6c009734b406)
https://github.com/quasarframework/quasar/commit/6c009734b406e246a0855ed060e3a822de8aecc1githubMentions a patch (unverified)
App Vite build cleanup can recursively remove unsafe configured output directories · Advisory · quasarframework/quasar · GitHub
https://github.com/quasarframework/quasar/security/advisories/GHSA-q9mq-245r-4g93Vendor Advisories for CVE-2026-106109(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| @quasar/app-vite | — |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-06 20:16 UTCEG score recompute
- 2026-10-06 19:54 UTCEG score recompute
- 2026-10-06 18:31 UTCEG score recompute
- 2026-10-06 17:37 UTCEG score recompute
- 2026-10-06 17:37 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
3 shownnpm:@quasar/app-vite
Frequently asked(4)
What is CVE-2026-106109?
CVE-2026-106109 is a medium vulnerability published on October 6, 2026. Quasar Framework is a framework for building high-performance Vue.js user interfaces. From 1.0.0 until 3.3.0, @quasar/app-vite recursively removed the resolved build.distDir before building without rejecting the project root, user home directory, filesystem roots, or symlink-resolved external…
When was CVE-2026-106109 disclosed?
CVE-2026-106109 was first published on October 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-106109?
CVE-2026-106109 has a CVSS base score of 4.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-106109?
A fix for CVE-2026-106109 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-106109 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-106109
Is Your Infrastructure Affected by CVE-2026-106109?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.