Is CVE-2026-8621 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-8621 being exploited in the wild.

How severe is CVE-2026-8621?

High severity, with a CVSS score of 8.8, published 14 May 2026.

Which products and versions are affected?

github.com/openclaw/crabbox (Go) < 0.12.0, SEMVER:introduced=0,fixed=0.12.0; Openclaw Crabbox < 0.12.0.

Is there a fix for CVE-2026-8621?

Yes. github.com/openclaw/crabbox (Go): upgrade to 0.12.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-8621 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-8621?

Check whether you run github.com/openclaw/crabbox (Go) or Openclaw Crabbox at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-8621: openclaw Crabbox authentication bypass via identity header spoofing

Q: Is there a fix for CVE-2026-8621?

Yes. github.com/openclaw/crabbox (Go): upgrade to 0.12.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-8621 attacked?

It is attacked over the network, in a hosted service.

Q: Am I affected by CVE-2026-8621?

Check whether you run github.com/openclaw/crabbox (Go) or Openclaw Crabbox at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-8621 · Severity: high · CVSS 8.8 · Published 2026-05-14

Crabbox, a tool used for managing cloud-based development environments and leases, contains a security flaw in how it handles shared authentication tokens. An attacker with a valid shared token can impersonate other users or organizations by including fake identity information in their web requests. This allows the attacker to view, modify, or manage resources belonging to other accounts, potentially leading to unauthorized data access or service disruption.

Technologies: github.com/openclaw/crabbox (Go), Openclaw Crabbox. Vendors: Go, Openclaw.

Quick answers

Is CVE-2026-8621 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-8621 being exploited in the wild.
How severe is CVE-2026-8621?: High severity, with a CVSS score of 8.8, published 14 May 2026.
Which products and versions are affected?: github.com/openclaw/crabbox (Go) < 0.12.0, SEMVER:introduced=0,fixed=0.12.0; Openclaw Crabbox < 0.12.0.
Is there a fix for CVE-2026-8621?: Yes. github.com/openclaw/crabbox (Go): upgrade to 0.12.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-8621 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-8621?: Check whether you run github.com/openclaw/crabbox (Go) or Openclaw Crabbox at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/openclaw/crabbox (Go): upgrade to 0.12.0 or later
```
go get github.com/openclaw/crabbox@v0.12.0
```

Technical details

An authentication bypass vulnerability exists in Crabbox's coordinator component due to improper validation of identity headers when using shared-token authentication. The `authenticateRequest()` function incorrectly trusts caller-supplied `X-Crabbox-Owner` and `X-Crabbox-Org` headers for requests authenticated with a valid `CRABBOX_SHARED_TOKEN`. An attacker with low privileges (possession of a shared token) can inject these headers to spoof their identity as a victim user or organization. This allows the attacker to bypass authorization checks and perform owner-scoped operations, such as reading lease details or managing resources belonging to others. The vulnerability is fixed in version 0.12.0 by ignoring these headers for shared-token callers and instead using server-controlled identity sources.

Affected products

openclaw Crabbox < 0.12.0

Identifiers

CVE-2026-8621
GHSA-4g9m-rffv-h6wq
GO-2026-5120

Timeline

2026-05-10: other: Fix submitted via pull request
2026-05-12: patched: Version 0.12.0 released
2026-05-14: disclosed: CVE published and advisory released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.