CVE-2026-106105
Severity not reportedQuasar Framework is a framework for building high-performance Vue.js user interfaces.
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
Not reported by the source (unknown — not "none").
Weakness classification (CWE)
Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.
Mitigation & advisories
No vendor advisory or patch reference tagged by NVD. Check the references below.
References
- https://github.com/quasarframework/quasar/commit/b719460aa78e88714b8a1b7ca68267234d217575 security-advisories@github.com
- https://github.com/quasarframework/quasar/releases/tag/@quasar/app-vite-v3.3.0 security-advisories@github.com
- https://github.com/quasarframework/quasar/releases/tag/@quasar/cli-v5.0.4 security-advisories@github.com
- https://github.com/quasarframework/quasar/security/advisories/GHSA-fh39-c73x-5pjv security-advisories@github.com