Vulnerabilities in pkg:npm/@quasar/app-vite

PACKAGE
Advisory Identifier: GHSA-fh39-c73x-5pjv
Advisory Summary

CVE-2026-106105 is a HIGH development tls private keys are vulnerability (CWE-732: Incorrect Permission Assignment for Critical Resource) affecting Quasar Framework libraries in the npm ecosystem. The issue involves development tls private keys are cached with overly permissive filesystem permissions. Remediation is available by upgrading affected packages to version 2.1.0, 5.0.4, 3.3.0.

5 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/@quasar/app-vite

5 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/@quasar/app-vite. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-fh39-c73x-5pjv CVE-2026-106105 HIGH Quasar Framework: Development TLS private keys are cached with overly permissive filesystem permissions
GHSA-r5mf-4r5x-q78f CVE-2026-106106 HIGH Quasar Framework: SSR/SSG dev error page discloses the full shell environment and its </script> escape is bypassable
GHSA-5m6h-8g35-p3m7 CVE-2026-106107 HIGH Quasar Framework: App Vite SSR and SSG nonce attributes are not safely constrained
GHSA-vhhq-m2gm-rwc9 CVE-2026-106108 MODERATE Quasar Framework: App Vite SSG page output paths can escape the configured distribution directory
GHSA-q9mq-245r-4g93 CVE-2026-106109 MODERATE Quasar Framework: App Vite build cleanup can recursively remove unsafe configured output directories

CVE-2026-106105 at a Glance

CVE Identifier CVE-2026-106105
GHSA Identifier GHSA-fh39-c73x-5pjv
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-732: Incorrect Permission Assignment for Critical Resource
Affected Product Quasar Framework
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-106105

To remediate this vulnerability, upgrade all affected Quasar Framework dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@quasar/ssl-certificate fixed: 2.1.0
npm install @quasar/ssl-certificate@2.1.0
@quasar/cli fixed: 5.0.4
npm install @quasar/cli@5.0.4
@quasar/app-vite fixed: 3.3.0
npm install @quasar/app-vite@3.3.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @quasar/ssl-certificate

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-106105, inspect your project dependencies using npm:

npm ls @quasar/ssl-certificate

Analyze the terminal output to locate any version of Quasar Framework in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.1.0), your application is affected.

Note: The npm ls @quasar/ssl-certificate command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-732: Incorrect Permission Assignment for Critical Resource, where the product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors. In Quasar Framework, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

The `@quasar/ssl-certificate` development utility caches a combined PEM containing a generated private key and certificate without explicitly restricting its filesystem permissions. On systems with a typical process umask, the PEM can be readable by other local users. A local attacker with filesystem access could copy and reuse the private key to impersonate a development TLS endpoint in an environment that trusts the certificate. The generated certificate was also unnecessarily CA-capable and included broad key usages beyond its localhost HTTPS purpose. Its IPv6 loopback entry was encoded as a DNS name rather than an IP subject alternative name. The remediation writes and repairs the cached PEM with owner-only permissions on supported platforms, generates a non-CA server-auth leaf certificate with constrained key usage, corrects the IPv6 loopback SAN, and bases cache expiry on content modification time so permission metadata changes cannot extend the certificate lifetime. This issue does not expose the key remotely by itself; exploitation requires another local user to be able to read the cached PEM file.

CVE-2026-106105 Affected Quasar Framework Versions

3 component(s)
Fixed Versions:
2.1.05.0.43.3.0
Product / Package Ecosystem Affected Versions Fixed Version
@quasar/ssl-certificate
npm
< 2.1.0
2.1.0
@quasar/cli
npm
< 5.0.4
5.0.4
@quasar/app-vite
npm
< 3.3.0
3.3.0

References

Frequently Asked Questions

What is CVE-2026-106105?
CVE-2026-106105 is a security vulnerability in Quasar Framework involving Development TLS private keys are cached with overly permissive filesystem permissions under CWE-732: Incorrect Permission Assignment for Critical Resource.
Which Quasar Framework versions are affected?
Affected versions include releases prior to 2.1.0, 5.0.4, 3.3.0 across affected packages: @quasar/ssl-certificate, @quasar/cli, @quasar/app-vite.
What version fixes CVE-2026-106105?
Upgrading to 2.1.0, 5.0.4, 3.3.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @quasar/ssl-certificate affected?
Yes, @quasar/ssl-certificate is affected in releases prior to 2.1.0. Upgrade your dependency to 2.1.0 or later.
Is @quasar/cli affected?
Yes, @quasar/cli is affected in releases prior to 5.0.4. Upgrade your dependency to 5.0.4 or later.
What CWE is associated with CVE-2026-106105?
CVE-2026-106105 is classified under CWE-732: Incorrect Permission Assignment for Critical Resource (The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.).
How can I check npm dependencies for CVE-2026-106105?
Run the dependency tree command: 'npm ls @quasar/ssl-certificate'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-fh39-c73x-5pjv",
  "modified" : "2026-10-07T16:16:18Z",
  "published" : "2026-10-07T16:16:18Z",
  "aliases" : [ "CVE-2026-106105" ],
  "summary" : "Quasar Framework: Development TLS private keys are cached with overly permissive filesystem permissions",
  "details" : "The `@quasar/ssl-certificate` development utility caches a combined PEM containing a generated private key and certificate without explicitly restricting its filesystem permissions. On systems with a typical process umask, the PEM can be readable by other local users. A local attacker with filesystem access could copy and reuse the private key to impersonate a development TLS endpoint in an environment that trusts the certificate.\n\nThe generated certificate was also unnecessarily CA-capable and included broad key usages beyond its localhost HTTPS purpose. Its IPv6 loopback entry was encoded as a DNS name rather than an IP subject alternative name.\n\nThe remediation writes and repairs the cached PEM with owner-only permissions on supported platforms, generates a non-CA server-auth leaf certificate with constrained key usage, corrects the IPv6 loopback SAN, and bases cache expiry on content modification time so permission metadata changes cannot extend the certificate lifetime. This issue does not expose the key remotely by itself; exploitation requires another local user to be able to read the cached PEM file.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@quasar/ssl-certificate"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.1.0"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2.0.0"
    }
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@quasar/cli"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "5.0.4"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 5.0.3"
    }
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@quasar/app-vite"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.3.0"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.2.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/quasarframework/quasar/security/advisories/GHSA-fh39-c73x-5pjv"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-106105"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/quasarframework/quasar/commit/b719460aa78e88714b8a1b7ca68267234d217575"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/quasarframework/quasar"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/quasarframework/quasar/releases/tag/@quasar/app-vite-v3.3.0"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/quasarframework/quasar/releases/tag/@quasar/cli-v5.0.4"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-732" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-07T16:16:18Z",
    "nvd_published_at" : "2026-10-06T18:16:51Z"
  }
}