High severity · published Oct 6, 2026
CVE-2026-106105
Quasar Framework: Development TLS private keys are cached with overly permissive filesystem permissions
8.4
CVSS
0.1%
EPSS
No
On KEV
Description
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.
Exploitation
Is it being used?
Exploit prediction (EPSS)0.1% · higher than 0% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
AP
app-vite · @quasar
< 3.3.0 · source: vendor
CL
cli · @quasar
< 5.0.4 · source: vendor
QU
quasar · quasarframework
< 2.23.3 · source: vendor
SS
ssl-certificate · @quasar
< 2.1.0 · source: vendor
Affected product
AP
app-vite
@quasar
More from app-vite
8.3
CVE-2026-106107
Quasar Framework: App Vite SSR and SSG nonce attributes are not safely constrained
7.1
CVE-2026-106106
Quasar Framework: SSR/SSG dev error page discloses the full shell environment and its </script> escape is bypassable
5.7
CVE-2026-106108
Quasar Framework: App Vite SSG page output paths can escape the configured distribution directory
4.1
CVE-2026-106109
Quasar Framework: App Vite build cleanup can recursively remove unsafe configured output directories