← Back
MAL-2026-4805
Vulnerability in metricflow-tracker (MAL-2026-4805)
Summary
vulnerability in metricflow-tracker (MAL-2026-4805). Risk of unauthorized operations or information disclosure. Exploitable via ``Metricflow``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **MAL-2026-4805** has been found in metricflow-tracker.
Attackers can target a specific entry point like ``Metricflow`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "metricflow-tracker MAL-2026-4805" on the vendor's site.
MAL-2026-4805 (metricflow-tracker) —
Attack surface: `Metricflow` / `serverUrl` / `document.head` / `window.MetricflowConfig.collectUrl`
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** (unclassified) exists in metricflow-tracker. Attackers reach the vulnerable code path via ``Metricflow`` without authentication.
📍 Affected scope
metricflow-tracker — . Attack surface: `Metricflow` / `serverUrl` / `document.head` / `window.MetricflowConfig.collectUrl`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ 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 'metricflow-tracker' .` 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 'metricflow-tracker' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `metricflow-tracker` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
metricflow-tracker