Quasar Framework is a framework for building high-performance Vue.js user interfaces. Prior to @quasar/ssl-certificate 2.1.0, @quasar/cli 5.0.4, and @quasar/app-vite 3.3.0, the @quasar/ssl-certificate utility cached a combined private key and certificate PEM without explicitly applying owner-only filesystem permissions. Another local user able to read the cache can copy the key and impersonate a development TLS endpoint in an environment that trusts the certificate. The generated certificate was also CA-capable, carried unnecessarily broad key usages, and encoded the IPv6 loopback address as a DNS subject alternative name. This issue is fixed in @quasar/ssl-certificate 2.1.0, @quasar/cli 5.0.4, and @quasar/app-vite 3.3.0.
CVE-2026-106105
HIGHPre-NVD 8.48.4
EchelonGraph scoreLOW confidence
This high-severity CVE scores 8.4 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
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 8.4Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 8.4
- EG Score
- 8.4HIGHlow confidence
- EG Risk
- 38EG Risk 38/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 computedSeverity84% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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 b719460aa78e (quasarframework/quasar)
Patch available: quasarframework/quasar quasar-v2.26.0 (contains commit b719460aa78e)
https://github.com/quasarframework/quasar/commit/b719460aa78e88714b8a1b7ca68267234d217575githubMentions a patch (unverified)
Development TLS private keys are cached with overly permissive filesystem permissions · Advisory · quasarframework/quasar · GitHub
https://github.com/quasarframework/quasar/security/advisories/GHSA-fh39-c73x-5pjvVendor Advisories for CVE-2026-106105(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(3 across 1 ecosystem)
npm(3)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| @quasar/app-vite | — |
| — |
| @quasar/cli | — |
| — |
| @quasar/ssl-certificate | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× 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 18:31 UTCEG score recompute
- 2026-10-06 18:02 UTCEG score recompute
- 2026-10-06 17:26 UTCEG score recompute
- 2026-10-06 17:25 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
3 shownnpm:@quasar/app-vite
Frequently asked(4)
What is CVE-2026-106105?
CVE-2026-106105 is a high vulnerability published on October 6, 2026. Quasar Framework is a framework for building high-performance Vue.js user interfaces. Prior to @quasar/ssl-certificate 2.1.0, @quasar/cli 5.0.4, and @quasar/app-vite 3.3.0, the @quasar/ssl-certificate utility cached a combined private key and certificate PEM without explicitly applying owner-only…
When was CVE-2026-106105 disclosed?
CVE-2026-106105 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-106105?
CVE-2026-106105 has a CVSS base score of 8.4 (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-106105?
A fix for CVE-2026-106105 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-106105 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-106105
Is Your Infrastructure Affected by CVE-2026-106105?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.