Skip to main content
Vulnerability Database/CVE-2026-106105

CVE-2026-106105: Quasar Framework Information Disclosure

CVE-2026-106105 is an information disclosure flaw in Quasar Framework where SSL certificates were cached without proper permissions, allowing local users to access private keys. This article covers technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-106105 Overview

CVE-2026-106105 affects the Quasar Framework, a Vue.js-based toolkit for building high-performance user interfaces. The @quasar/ssl-certificate utility cached a combined private key and certificate PEM file without enforcing owner-only filesystem permissions. Any local user with read access to the cache directory can retrieve the private key and impersonate development TLS endpoints trusted by the certificate. The generated certificate also carried CA-capable flags, excessive key usages, and encoded the IPv6 loopback as a DNS subject alternative name, broadening its potential misuse. The flaw is tracked under [CWE-732: Incorrect Permission Assignment for Critical Resource].

Critical Impact

A local attacker with read access to the Quasar development cache can steal the cached TLS private key and impersonate a trusted development HTTPS endpoint without triggering certificate warnings.

Affected Products

  • @quasar/ssl-certificate prior to version 2.1.0
  • @quasar/cli prior to version 5.0.4
  • @quasar/app-vite prior to version 3.3.0

Discovery Timeline

  • 2026-10-06 - CVE-2026-106105 published to NVD
  • 2026-10-06 - Last updated in NVD database

Technical Details for CVE-2026-106105

Vulnerability Analysis

The @quasar/ssl-certificate utility generates a self-signed TLS certificate for local development servers. The utility writes the combined private key and certificate to a cache file using default filesystem permissions. On most POSIX systems, default umask values produce world-readable files, exposing the private key to any local account on the host.

An attacker with local shell access or any process running under a different user account can read the cached PEM. With the private key in hand, the attacker stands up a rogue TLS endpoint on localhost or ::1 and presents the stolen certificate. Browsers, test harnesses, and other tools that have added the development certificate to their trust store will complete the handshake without warning.

Two compounding issues increase impact. The generated certificate was marked CA-capable, meaning it can sign additional certificates for arbitrary hosts if trusted as a root. The certificate also carried broad keyUsage and extendedKeyUsage extensions and encoded the IPv6 loopback address ::1 as a DNS Subject Alternative Name rather than an IP SAN, which may bypass hostname validation logic in some clients.

Root Cause

The root cause is the omission of an explicit chmod call when persisting the private key. The utility imported write functions from node:fs but did not include chmodSync, so permissions were left to the operating system default. Combined with certificate generation defaults that enabled CA constraints and permissive key usages, a local information disclosure escalated into a full TLS impersonation primitive.

Attack Vector

Exploitation requires local access to the host where a Quasar developer has executed a project using the affected tooling. The attacker reads the cached PEM, extracts the private key, and launches a listener bound to the loopback interface. When the developer or any trusting client connects, the attacker intercepts, modifies, or injects traffic over the TLS session.

javascript
// Security patch in utils/ssl-certificate/src/index.js
-import { existsSync, readFileSync, statSync, writeFileSync } from 'node:fs'
+import {
+  chmodSync,
+  existsSync,
+  readFileSync,
+  statSync,
+  writeFileSync
+} from 'node:fs'
 import fse from 'fs-extra'
 import { generate } from 'selfsigned'

The fix adds chmodSync so the utility can explicitly restrict the cached PEM to owner-only read and write access. Source: GitHub Commit b719460.

Detection Methods for CVE-2026-106105

Indicators of Compromise

  • World-readable or group-readable PEM files inside Quasar SSL certificate cache directories under developer home paths.
  • Unexpected processes bound to TCP port 443, 8080, or other development ports on 127.0.0.1 or ::1 that are not the Quasar dev server.
  • Self-signed certificates in trust stores with basicConstraints: CA:TRUE and ::1 listed as a DNS SAN.

Detection Strategies

  • Audit filesystem permissions on known Quasar cache paths and flag any PEM files not restricted to mode 0600.
  • Inventory installed @quasar/cli, @quasar/app-vite, and @quasar/ssl-certificate versions across developer workstations and build runners.
  • Inspect generated certificates for CA-capable flags and loopback addresses encoded as DNS SANs instead of IP SANs.

Monitoring Recommendations

  • Monitor file access events on developer home directories for cross-user reads of .pem, .key, or Quasar cache artifacts.
  • Alert on new listeners binding to loopback addresses outside expected development workflows on shared or multi-tenant hosts.
  • Track package manager install events that pin vulnerable versions of the affected Quasar packages.

How to Mitigate CVE-2026-106105

Immediate Actions Required

  • Upgrade to @quasar/ssl-certificate 2.1.0, @quasar/cli 5.0.4, and @quasar/app-vite 3.3.0 or later.
  • Delete any existing cached PEM files generated by vulnerable versions and regenerate certificates after upgrading.
  • Remove previously generated Quasar development certificates from browser and system trust stores.

Patch Information

The maintainers resolved the issue by importing chmodSync and restricting the cached PEM to owner-only permissions, tightening certificate generation defaults, and correcting the SAN encoding. Review the fix details in the GitHub Security Advisory GHSA-fh39-c73x-5pjv, the Quasar CLI v5.0.4 Release, and the Quasar App Vite v3.3.0 Release.

Workarounds

  • Manually set permissions on the cached PEM file to 0600 after each generation if an immediate upgrade is not possible.
  • Avoid running Quasar development builds on shared or multi-user hosts until all affected packages are updated.
  • Do not add Quasar-generated development certificates to system-wide trust stores; scope trust to a single browser profile.
bash
# Restrict permissions on existing cached certificates as an interim workaround
find ~/.quasar -type f \( -name '*.pem' -o -name '*.key' \) -exec chmod 600 {} \;

# Upgrade affected packages
npm install --save-dev @quasar/app-vite@^3.3.0
npm install -g @quasar/cli@^5.0.4

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.