[ CVE-2026-106105 · Published 6 Oct 2026 ]
Quasar Framework: Development TLS private keys are cached with overly permissive filesystem permissions
[ Description ]Official 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.
[ Fixes ]Fixes and patches
- @quasar/ssl-certificate 2.1.0Fixed version · GitHub Advisories · npm package @quasar/ssl-certificate: upgrade to 2.1.0 or later (affected <= 2.0.0)
- @quasar/cli 5.0.4Fixed version · GitHub Advisories · npm package @quasar/cli: upgrade to 5.0.4 or later (affected <= 5.0.3)
- @quasar/app-vite 3.3.0Fixed version · GitHub Advisories · npm package @quasar/app-vite: upgrade to 3.3.0 or later (affected <= 3.2.0)
[ Packages ]Affected open-source packages
- @quasar/ssl-certificate npmAffected <= 2.0.0 · fixed in 2.1.0 · GHSA-fh39-c73x-5pjv
- @quasar/cli npmAffected <= 5.0.3 · fixed in 5.0.4 · GHSA-fh39-c73x-5pjv
- @quasar/app-vite npmAffected <= 3.2.0 · fixed in 3.3.0 · GHSA-fh39-c73x-5pjv