PoC Monitor
← All CVEs
CVE-2026-106105published 6 Oct 2026 17:20 UTCData: JSON · API

Quasar

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.4high · scored by CNA · CWE-732
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

quasarframework quasar
  • < 2.23.3

Fixed in 2.23.3

@quasar app-vite
  • < 3.3.0

Fixed in 3.3.0

@quasar cli
  • < 5.0.4

Fixed in 5.0.4

@quasar ssl-certificate
  • < 2.1.0

Fixed in 2.1.0

Mitigation

Upgrade quasar to 2.23.3 or later.

Upgrade app-vite to 3.3.0 or later.

Upgrade cli to 5.0.4 or later.

Upgrade ssl-certificate to 2.1.0 or later.

References

1 more

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published6 Oct 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.