Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
7.6
CVE-2026-106105: Quasar Framework development TLS keys readable by other users
CVE-2026-106105 · published 29 days ago
Summary
The Quasar development tools stored private TLS keys in a cache without restricting file access, so any local user could read them. This could let an attacker impersonate a development server that trusts the certificate. Update to the latest versions of the Quasar packages to apply proper file permissions and stop the risk.
What to do
- Update quasar ssl-certificate to version 2.1.0.
- Update quasar cli to version 5.0.4.
- Update quasar app-vite to version 3.3.0.
- Update quasar @quasar/ssl-certificate to version 2.1.0.
- Update quasar @quasar/cli to version 5.0.4.
- Update quasar @quasar/app-vite to version 3.3.0.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| – | quasarframework | quasar | < 2.23.3 |
| – | @quasar | app-vite | < 3.3.0 |
| – | @quasar | cli | < 5.0.4 |
| – | @quasar | ssl-certificate | < 2.1.0 |
| npm | quasar | ssl-certificate |
<= 2.0.0 Fix: upgrade to 2.1.0
|
| npm | quasar | cli |
<= 5.0.3 Fix: upgrade to 5.0.4
|
| npm | quasar | app-vite |
<= 3.2.0 Fix: upgrade to 3.3.0
|
| npm | quasar | @quasar/ssl-certificate |
< 2.1.0 Fix: upgrade to 2.1.0
|
| npm | quasar | @quasar/cli |
< 5.0.4 Fix: upgrade to 5.0.4
|
| npm | quasar | @quasar/app-vite |
< 3.3.0 Fix: upgrade to 3.3.0
|
Original advisory text
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.
References
- https://github.com/advisories/GHSA-fh39-c73x-5pjv
- https://github.com/quasarframework/quasar Product
- https://github.com/quasarframework/quasar/releases/tag/@quasar/app-vite-v3.3.0 URL
- https://github.com/quasarframework/quasar/releases/tag/@quasar/cli-v5.0.4 URL
- https://github.com/quasarframework/quasar/security/advisories/GHSA-fh39-c73x-5pj... Vendor Advisory
- https://github.com/quasarframework/quasar/commit/b719460aa78e88714b8a1b7ca682672... Patch
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/106xxx/CVE-2026-1061... Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-106105 Vendor Advisory
Severity
7.6
High
Type
CWE-732Incorrect Permission Assignment for Critical Resource
Timeline
Published6 Oct 2026
Updated21 Oct 2026
First seen6 Oct 2026
Sources
CVE-2026-106105 · NVD
CVE-2026-106105 · MITRE
CVE-2026-106105 · OSV
GHSA-fh39-c73x-5pjv · GHSA
GHSA-fh39-c73x-5pjv · OSV
Track software like this
Free during beta