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