Crabbox: authentication bypass vulnerability that allows impersonation of others by spoofing identity headersGHSA-4g9m-rffv-h6wq
HIGHFix: openclaw/crabbox#70GHSA-4g9m-rffv-h6wq is a high-severity (CVSS 8.8) Improper Authentication vulnerability in github.com/openclaw/crabbox. A fix is available for github.com/openclaw/crabbox — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-4g9m-rffv-h6wq.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/openclaw/crabboxReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/openclaw/crabbox | all versions | 0.12.0go get github.com/openclaw/crabbox@v0.12.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/openclaw/crabbox, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/openclaw/crabbox to 0.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4g9m-rffv-h6wq is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is GHSA-4g9m-rffv-h6wq in your dependencies?
Find it across Go, including transitive dependencies.