CVE-2026-106105: Quasar Framework: Development TLS private keys are cached with overly permissive filesystem permissions
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
@quasar/ssl-certificateto a version that resolves this vulnerability.Fixed in 2.1.0 - Upgrade
Upgrade
@quasar/clito a version that resolves this vulnerability.Fixed in 5.0.4 - Upgrade
Upgrade
@quasar/app-viteto a version that resolves this vulnerability.Fixed in 3.3.0