How severe is GHSA-fh39-c73x-5pjv?

No CVSS score has been assigned to GHSA-fh39-c73x-5pjv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-fh39-c73x-5pjv?

GHSA-fh39-c73x-5pjv affects the following packages: @quasar/ssl-certificate (npm), @quasar/cli (npm), @quasar/app-vite (npm). Ecosystems affected: npm.

How do I fix GHSA-fh39-c73x-5pjv?

Update @quasar/ssl-certificate to 2.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fh39-c73x-5pjv is resolved across your whole dependency graph.

How do I detect GHSA-fh39-c73x-5pjv in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @quasar/ssl-certificate, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-fh39-c73x-5pjv if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-fh39-c73x-5pjv actively exploited in the wild?

No public exploit code has been indexed for GHSA-fh39-c73x-5pjv yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-fh39-c73x-5pjv?

GHSA-fh39-c73x-5pjv has an EPSS (Exploit Prediction Scoring System) score of 0.1%, placing it in the 0th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-fh39-c73x-5pjv?

GHSA-fh39-c73x-5pjv is classified as CWE-732 (CWE-732). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-fh39-c73x-5pjv published, and has it been updated?

GHSA-fh39-c73x-5pjv was published on October 7, 2026 and was last updated on October 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Quasar Framework: Development TLS private keys are cached with overly permissive filesystem permissionsGHSA-fh39-c73x-5pjv

Fix: quasarframework/quasar@b719460

GHSA-fh39-c73x-5pjv is a CWE-732 vulnerability in @quasar/ssl-certificate. A fix is available for @quasar/ssl-certificate — see the affected versions and patch details below.

Also known asCVE-2026-106105

Published

Oct 7, 2026

Updated

Oct 7, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs0th percentile — riskier than 0% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

6other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@quasar/ssl-certificatenpm

125Kdownloads / week

@quasar/clinpm

27Kdownloads / week

@quasar/app-vitenpm

186Kdownloads / week

Description

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.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@quasar/ssl-certificate`	all versions	2.1.0`npm install @quasar/ssl-certificate@2.1.0`
📦npm	`@quasar/cli`	all versions	5.0.4`npm install @quasar/cli@5.0.4`
📦npm	`@quasar/app-vite`	all versions	3.3.0`npm install @quasar/app-vite@3.3.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @quasar/ssl-certificate, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @quasar/ssl-certificate to 2.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fh39-c73x-5pjv is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-fh39-c73x-5pjv in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works