NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2026-106105: Quasar Framework: Development TLS private keys are cached with overly permissive filesystem permissions

highCVSS 4.0 8.4GHSA-fh39-c73x-5pjv

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.

Published Oct 7, 2026

Affected packages

@quasar/ssl-certificate

Ecosystem
npm
Affected
<= 2.0.0
Fixed in
2.1.0
Check
npm ls @quasar/ssl-certificate

@quasar/cli

Ecosystem
npm
Affected
<= 5.0.3
Fixed in
5.0.4
Check
npm ls @quasar/cli

@quasar/app-vite

Ecosystem
npm
Affected
<= 3.2.0
Fixed in
3.3.0
Check
npm ls @quasar/app-vite

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

Credited to hawkeye64.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries