Skip to main content
VulnerabilityPublished

CVE-2026-106105: quasarframework quasar · Incorrect Permissions

Affects quasarframework quasarSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.4 High : upgrade to 2.23.3 soon.

Data as of 20 Nov 2026, 17:34 UTC

CVSS 4.0 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
quasarframeworkquasarAffected
  • <2.23.3
Fixed in
  • 2.23.3
@quasarapp-viteAffected
  • <3.3.0
Fixed in
  • 3.3.0
@quasarcliAffected
  • <5.0.4
Fixed in
  • 5.0.4
@quasarssl-certificateAffected
  • <2.1.0
Fixed in
  • 2.1.0

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

Community reviews

Loading reviews…