Vulnerability in @quasar/ssl-certificate (CVE-2026-106105)
Summary
Vulnerability in @quasar/ssl-certificate (CVE-2026-106105). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.1.0 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-106105 has been found in @quasar/ssl-certificate.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @quasar/ssl-certificate to 2.1.0 or later.
If unsure, ask your IT team or search "@quasar/ssl-certificate CVE-2026-106105" on the vendor's site.
CVE-2026-106105 (@quasar/ssl-certificate) — CWE-732
Patched: 2.1.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-732) exists in @quasar/ssl-certificate.
Check the vendor advisory for the affected versions of @quasar/ssl-certificate.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.1.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@quasar/ssl-certificate' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@quasar/ssl-certificate' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@quasar/ssl-certificateを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @quasar/ssl-certificate to 2.1.0ステージング環境で 2.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com