CVE-2026-106108

MEDIUMPre-NVD 5.75.7
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 5.7 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). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: a secondary CVSS source
5.7EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 5.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
5.7
EG Score
5.7MEDIUMlow confidence
EG Risk
26
EG Risk 26/100

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 computed (value × EchelonGraph’s weight)
Severity57% × 45%
The EG Score, 5.7 of 10.
Exploitation0% × 40%
No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 7, 2026

Last Modified

October 13, 2026

Advisory Details (2)

Auto-updated Oct 13, 2026
Patch available. Sources: github, github_commit.
GitHub commit Patch Available

commit cdd4daeec839 (quasarframework/quasar)

Patch available: quasarframework/quasar quasar-v2.27.0 (contains commit cdd4daeec839)

https://github.com/quasarframework/quasar/commit/cdd4daeec839215540221122763c7a17cd478abc
GitHub advisoryMentions a patch (unverified)

App Vite SSG page output paths can escape the configured distribution directory · Advisory · quasarframework/quasar · GitHub

https://github.com/quasarframework/quasar/security/advisories/GHSA-vhhq-m2gm-rwc9

Vendor Advisories for CVE-2026-106108(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)
PackageVulnerable rangeFix by version rangeDependents
@quasar/app-vite—
  • 3.1.0 up to 3.3.0: fixed in 3.3.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 10× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 21:46 UTCEG score recompute
  2. 2026-10-13 21:02 UTCEG score recompute
  3. 2026-10-13 15:29 UTCEG score recompute
  4. 2026-10-13 15:07 UTCEG score recomputeFirst assessed: 5.7 MEDIUM
  5. 2026-10-13 15:04 UTCMITRE cvelistV5CVSS v3 → 5.7 · CVSS v4 → 5.7
  6. 2026-10-12 16:39 UTCEG score recompute
  7. 2026-10-11 20:14 UTCEG score recompute
  8. 2026-10-11 18:27 UTCEG score recompute
  9. 2026-10-11 15:00 UTCEG score recompute
  10. 2026-10-07 16:26 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(4)

What is CVE-2026-106108?
CVE-2026-106108 is a medium-severity vulnerability; its CVE record was published on October 7, 2026. 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…
When was the CVE record for CVE-2026-106108 published?
The CVE record for CVE-2026-106108 was published on October 7, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 13, 2026; the record at its source may have been updated since.
What is the CVSS score of CVE-2026-106108?
CVE-2026-106108 has a CVSS base score of 5.7 (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-106108?
A fix for CVE-2026-106108 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-106108 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-106108

Explore →

Is Your Infrastructure Affected by CVE-2026-106108?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs