What’s Vulnerable › Vulnerabilities
CVE-2026-106105: Quasar Framework: Development TLS private keys are cached with overly permissive filesystem permissions
- Severity: high (CVSS 8.4 v4.0)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.1% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-10-06 · updated 2026-10-06
- Weakness: CWE-732
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.
Affected products
- @quasar app-vite: before 3.3.0
- @quasar cli: before 5.0.4
- @quasar ssl-certificate: before 2.1.0
- quasarframework quasar: before 2.23.3
References
- https://github.com/quasarframework/quasar/commit/b719460aa78e88714b8a1b7ca68267234d217575
- https://github.com/quasarframework/quasar/releases/tag/@quasar/app-vite-v3.3.0
- https://github.com/quasarframework/quasar/releases/tag/@quasar/cli-v5.0.4
- https://github.com/quasarframework/quasar/security/advisories/GHSA-fh39-c73x-5pjv
Get alerted when CVE-2026-106105 or the next vulnerability affects your stack