CVE-2026-106105 · GHSA-fh39-c73x-5pjv
Quasar Framework: Development TLS private keys are cached with overly permissive filesystem permissions
- Risk score
- 55/100
- CVSS
- 8.4 v4.0
- Exploit chance (30 days)
- 0.1%
- Published
- 6 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- 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 permission…
- Affected
- @quasar/ssl-certificate (npm) <= 2.0.0; @quasar/cli (npm) <= 5.0.3; @quasar/app-vite (npm) <= 3.2.0
- Fix
- Upgrade @quasar/ssl-certificate to 2.1.0; @quasar/cli to 5.0.4; @quasar/app-vite to 3.3.0 or later.
- Exploitation
- No known exploitation
Why it is Yellow
- CVSS 8.4 high
- On your watchlist: npm
Affected packages
| Package | Ecosystem | Vulnerable | Fixed in |
|---|---|---|---|
| @quasar/ssl-certificate | npm | <= 2.0.0 | 2.1.0 |
| @quasar/cli | npm | <= 5.0.3 | 5.0.4 |
| @quasar/app-vite | npm | <= 3.2.0 | 3.3.0 |
References
- https://github.com/advisories/GHSA-fh39-c73x-5pjv
- https://github.com/quasarframework/quasar/security/advisories/GHSA-fh39-c73x-5pjv
- https://nvd.nist.gov/vuln/detail/CVE-2026-106105
- 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/advisories/GHSA-fh39-c73x-5pjv
Original 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.
Last activity 6 Oct 2026. Patch Forecast updates every hour.