# CVE-2026-8621: Crabbox < v0.12.0 Authentication Bypass via Header Spoofing

> Attackers can bypass authentication by spoofing identity headers to access other users' lease operations in Crabbox.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 May 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-4g9m-rffv-h6wq, GO-2026-5120

## What is CVE-2026-8621?

CVE-2026-8621 is a high-severity authentication bypass vulnerability in openclaw crabbox, published on 14 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-8621?

3 open source packages ship an affected version, including github.com/openclaw/crabbox.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/openclaw/crabbox` | Go | All versions | 0.12.0 |
| `github.com/openclaw/crabbox` | Go | All versions | 0.12.0 |
| `github.com/openclaw/crabbox` | Go | All versions | 0.12.0 |

## How do I fix CVE-2026-8621?

Upgrade github.com/openclaw/crabbox to 0.12.0 or later.

## Is CVE-2026-8621 being exploited?

There is no known exploitation of CVE-2026-8621 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8621 and fix it if it is affected.

What it is: CVE-2026-8621 is a high-severity authentication bypass vulnerability in openclaw crabbox, published on 14 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-8621 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/openclaw/crabbox (Go): affected all versions; fixed in 0.12.0
- github.com/openclaw/crabbox (Go): affected all versions; fixed in 0.12.0
- github.com/openclaw/crabbox (Go): affected all versions; fixed in 0.12.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8621/ (Markdown: https://insights.sbomify.com/CVE-2026-8621/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8621
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8621
- OSV: https://osv.dev/vulnerability/CVE-2026-8621

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8621/
Summaries are generated and may contain mistakes; the official description above is the record.