← Back
CVE-2026-63004
medium
CVSS 5.5
SSRF (Server-Side Request Forgery) in unleash-server (CVE-2026-63004)
Summary
SSRF in unleash-server (CVE-2026-63004). Risk of unauthorized operations or information disclosure. Exploitable via `POST /api/admin/addons`. Mitigation: upgrade to `8.0.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-63004** has been found in unleash-server.
Attackers can target a specific entry point like `POST /api/admin/addons` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.5/10.
What to do: upgrade unleash-server to **8.0.2** or later.
If unsure, ask your IT team or search "unleash-server CVE-2026-63004" on the vendor's site.
CVE-2026-63004 (unleash-server) — CWE-918 / CVSS v3 5.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/admin/addons / `url` / `parameters.url` / `Authorization`
Patched: `8.0.2` — 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
**SSRF** (CWE-918) exists in unleash-server. Attackers reach the vulnerable code path via `POST /api/admin/addons` without authentication.
📍 Affected scope
unleash-server — . Attack surface: POST /api/admin/addons / `url` / `parameters.url` / `Authorization`.
🔥 Severity
Severity: Medium (CVSS 5.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **8.0.2**.
🛡️ 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 `POST /api/admin/addons` requests with malformed payloads or SQL meta-characters. Run `grep -r 'unleash-server' .` 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 'unleash-server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `unleash-server` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /api/admin/addons' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /api/admin/addons` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade unleash-server to 8.0.2ステージング環境で 8.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against POST /api/admin/addons on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
unleash-server
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.0.2"}]}]