CVE-2026-106105 json
Quasar Framework: Development TLS private keys are cached with overly permissive filesystem permissions
published last mo. modified last mo. also GHSA-fh39-c73x-5pjv , EUVD-2026-93570
- cvss
- 8.4
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 0%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm @quasar/ssl-certificate 2.1.0
- npm @quasar/cli 5.0.4
- npm @quasar/app-vite 3.3.0
Is CVE-2026-106105 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last mo.
Exploit prediction
0.07% chance of exploitation in the next 30 days, higher than 0% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.4 | CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N |
| CNA | 4.0 | 8.4 | CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | @quasar/ssl-certificate | <2.1.0 |
2.1.0 |
| npm | @quasar/cli | <5.0.4 |
5.0.4 |
| npm | @quasar/app-vite | <3.3.0 |
3.3.0 |
Affected products
- quasarframework quasar
- @quasar app-vite
- @quasar cli
- @quasar ssl-certificate
Classification
- Weakness
-
- CWE-732 Incorrect Permission Assignment for Critical Resource
References
-
github.com
/quasarframework/quasar/commit/b719460aa78e88714b8a1b7ca68267234d217575
web
-
github.com
/quasarframework/quasar/security/advisories/GHSA-fh39-c73x-5pjv
web
-
github.com
/quasarframework/quasar/releases/tag/@quasar/app-vite-v3.3.0
web
-
github.com
/quasarframework/quasar/releases/tag/@quasar/cli-v5.0.4
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-106105
advisory
-
github.com
/quasarframework/quasar
package
Sources
- CVE List CVE-2026-106105
- GitHub Advisory GHSA-fh39-c73x-5pjv
- NVD CVE-2026-106105
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.