CVE-2026-106105: CWE-732: Incorrect Permission Assignment for Critical Resource in quasarframework quasar
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.
CVSS v4.0
Score 8.4high
Affected software
quasarframework
quasar
@quasar
app-vite
@quasar
cli
@quasar
ssl-certificate
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability CVE-2026-106105 affects the Quasar Framework's @quasar/ssl-certificate utility and related packages. Prior to the fixed versions, the utility cached a combined private key and certificate PEM file without enforcing owner-only filesystem permissions. This misconfiguration allows any local user with read access to the cache to copy the private key and impersonate a development TLS endpoint in environments that trust the certificate. Additionally, the generated certificates were CA-capable with unnecessarily broad key usages and included the IPv6 loopback address as a DNS subject alternative name, which may increase risk. The issue is resolved by updating to @quasar/ssl-certificate 2.1.0, @quasar/cli 5.0.4, and @quasar/app-vite 3.3.0.
Potential Impact
Local users with read access to the cached private key and certificate can impersonate development TLS endpoints, potentially undermining TLS security in trusted environments. The CA-capable certificates with broad key usages increase the risk of misuse. This vulnerability compromises the confidentiality and integrity of development TLS communications.
Mitigation Recommendations
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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-10-06T15:33:55.333Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ac5310f2cdf04f656ca0fbc
Added to database: 10/06/2026, 17:34:07 UTC
Last enriched: 10/06/2026, 17:48:13 UTC
Last updated: 10/06/2026, 18:19:01 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.