← Back
CVE-2026-73647
medium
CVSS 5.6
Vulnerability in quasar (CVE-2026-73647)
Summary
vulnerability in quasar (CVE-2026-73647). Risk of unauthorized operations or information disclosure. Exploitable via ``__proto__``. Mitigation: upgrade to `2.22.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-73647** has been found in quasar.
Attackers can target a specific entry point like ``__proto__`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.6/10.
What to do: upgrade quasar to **2.22.0** or later.
If unsure, ask your IT team or search "quasar CVE-2026-73647" on the vendor's site.
CVE-2026-73647 (quasar) — CWE-1321 / CVSS v3 5.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `__proto__` / `constructor` / `prototype` / `Object.prototype`
Patched: `2.22.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.
❓ What is the problem
**A vulnerability** (CWE-1321) exists in quasar. Attackers reach the vulnerable code path via ``__proto__`` without authentication.
📍 Affected scope
quasar — . Attack surface: `__proto__` / `constructor` / `prototype` / `Object.prototype`.
🔥 Severity
Severity: Medium (CVSS 5.6/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.22.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'quasar' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'quasar' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `quasar` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade quasar to 2.22.0ステージング環境で 2.22.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
quasar
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.22.0"}]}]