Vulnerability · Published Oct 6, 2026 · Assigned by GitHub_M

CVE-2026-106105Quasar Framework: Development TLS private keys are cached with overly permissive filesystem permissions

High 8.4

In plain English

A high-severity incorrect permission assignment in app-vite from @quasar. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 0% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 4.0)8.4High
Exploit odds (30 days)<0.1%top 100.0% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official 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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
npm@quasar/app-vite3.3.0GHSA-fh39-c73x-5pjv
npm@quasar/cli5.0.4GHSA-fh39-c73x-5pjv
npm@quasar/ssl-certificate2.1.0GHSA-fh39-c73x-5pjv

Affected products (as reported)

VendorProductVersions
quasarframework quasar < 2.23.3
@quasar app-vite < 3.3.0
@quasar cli < 5.0.4
@quasar ssl-certificate < 2.1.0

Weakness: CWE-732 · Vector: 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

References