CVE-2026-8621: Crabbox < v0.12.0 Authentication Bypass via Header Spoofing
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.
Security readout for executives and security teams
Plain-English summary
Crabbox before v0.12.0 lets a shared-token user pretend to be another owner or organization by manipulating identity headers. That can expose or change lease operations belonging to other accounts. This is high urgency where Crabbox is internet-accessible or shared tokens are used across tenants.
Executive priority
Prioritize remediation promptly for any multi-tenant or externally reachable Crabbox deployment. The business risk is unauthorized access across account boundaries, not just local privilege escalation.
Technical view
The issue is CWE-287 authentication bypass. Requests authenticated with a non-admin shared token could supply X-Crabbox-Owner and X-Crabbox-Org values that authorization trusted for owner/org-scoped lease operations. CVSS 8.8 reflects network reachability, low complexity, low privileges, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is likely limited to organizations running openclaw Crabbox versions before v0.12.0, especially deployments using shared-token authentication for owner or organization scoped lease operations.
Exploitation context
The source bundle does not cite active exploitation or CISA KEV listing. Abuse requires a valid shared token, then relies on spoofed identity headers to cross authorization boundaries.
Researcher notes
Evidence supports affected versions before v0.12.0 and a patch commit b657323f1d1c954cefc8444571fa6c45a8896e7f. Public sources identify header spoofing, but the bundle does not provide independent exploit-in-the-wild confirmation.
Mitigation direction
Upgrade Crabbox to v0.12.0 or a later vendor-fixed release.
Rotate shared tokens that may have been exposed to untrusted users.
Restrict Crabbox network access to trusted clients while remediation is underway.
Review vendor release notes, pull request 70, and patch commit for operational guidance.
Validation and detection
Inventory Crabbox deployments and record exact running versions.
Confirm no production instance runs a version before v0.12.0.
Review access logs for unexpected owner or organization header values.
Verify shared-token callers cannot affect other owner or organization lease operations.
Check whether shared tokens are scoped and distributed only to trusted users.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-287: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-287 · source CWE mapping
Improper Authentication
Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.