Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-8621 high CVSS 8.8

Authentication Bypass in github.com/openclaw/crabbox (CVE-2026-8621)

Summary

Authentication bypass in github.com/openclaw/crabbox (CVE-2026-8621). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 0.12.0 or later.

Original description

The description as published by the source.

Crabbox prior to v0.12.0 contains an authentication bypass vulnerability that allows non-admin shared-token callers to impersonate other owners or organizations by spoofing identity headers. Attackers can inject malicious X-Crabbox-Owner and X-Crabbox-Org headers in requests authenticated with a shared token to bypass authorization checks and access owner/org-scoped lease operations belonging to victim accounts.

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-8621 has been found in github.com/openclaw/crabbox.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade github.com/openclaw/crabbox to 0.12.0 or later.
If unsure, ask your IT team or search "github.com/openclaw/crabbox CVE-2026-8621" on the vendor's site.

CVE-2026-8621 (github.com/openclaw/crabbox) — CWE-287 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.12.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

Authentication bypass (CWE-287) exists in github.com/openclaw/crabbox.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/openclaw/crabbox.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 0.12.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 'github.com/openclaw/crabbox' . 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

  1. 1
    Identify exposure identify 
    grep -r 'github.com/openclaw/crabbox' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/openclaw/crabbox を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/openclaw/crabbox to 0.12.0

    ステージング環境で 0.12.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/openclaw/crabbox
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.12.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details