cve.bz

CVE-2026-106105

8.4 highEPSS 0.07%Fix available

High (8.4). EPSS 0.07% estimated probability of exploitation activity in the next 30 days. Fixed in @quasar/ssl-certificate 2.1.0.

On this page
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.

Severity

CVSS 4.0

8.4 high
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
EPSS
0.07% (unchanged from 0.07% a week ago; 0.07% 30 days ago) estimated probability of exploitation activity in the next 30 days; 0th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-732 Incorrect Permission Assignment for Critical Resource
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • @quasar/ssl-certificate (npm): fixed in 2.1.0
  • @quasar/cli (npm): fixed in 5.0.4
  • @quasar/app-vite (npm): fixed in 3.3.0

Ask an AI about this CVE

Show the promptExplain CVE-2026-106105 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-106105?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-106105?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-106105 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

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

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-fh39-c73x-5pjvnpm@quasar/ssl-certificate<2.1.02.1.0
GHSA-fh39-c73x-5pjvnpm@quasar/cli<5.0.45.0.4
GHSA-fh39-c73x-5pjvnpm@quasar/app-vite<3.3.03.3.0

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-732 (11).

References

Check your stackJSON