CVE-2026-106105: quasarframework quasar · Incorrect Permissions
Affects quasarframework quasarSource CVE Database V5
Not known to be exploited · CVSS 8.4 High : upgrade to 2.23.3 soon.
Data as of 20 Nov 2026, 17:34 UTC
- EPSS
- 0.06% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.23.3, 3.3.0, 5.0.4 +1
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| quasarframeworkquasar | Affected
| Fixed in
|
| @quasarapp-vite | Affected
| Fixed in
|
| @quasarcli | Affected
| Fixed in
|
| @quasarssl-certificate | Affected
| Fixed in
|
AI-suggested
This vulnerability is fixed in @quasar/ssl-certificate 2.1.0, @quasar/cli 5.0.4, and @quasar/app-vite 3.3.0. Users should upgrade to these versions or later to ensure proper permission assignment on cached certificates and keys and to avoid the risks associated with the flawed certificate generation. No additional mitigations are indicated by the vendor advisory.
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.
References
- github.com/quasarframework/quasar/security/advisories/GHSA-fh39-c73x-5pjv (opens in a new tab)
- github.com/quasarframework/quasar/commit/b719460aa78e88714b8a1b7ca68267234d217575 (opens in a new tab)
- github.com/quasarframework/quasar/releases/tag/@quasar/app-vite-v3.3.0 (opens in a new tab)
- github.com/quasarframework/quasar/releases/tag/@quasar/cli-v5.0.4 (opens in a new tab)