Quick answers
- Is CVE-2026-8629 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-8629 being exploited in the wild.
- How severe is CVE-2026-8629?
- High severity, with a CVSS score of 8.1, published 14 May 2026.
- Which products and versions are affected?
- Openclaw Crabbox < 0.12.0, < v0.12.0.
- Is there a fix for CVE-2026-8629?
- A patch was published on 2026-05-11: Fix merged into main branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-8629 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-8629?
- Check whether you run 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.
Technical details
A privilege escalation vulnerability exists in Crabbox due to insufficient access control checks in the ticket-minting endpoints. Specifically, the /v1/leases/:id/code/ticket, /v1/leases/:id/webvnc/ticket, and /v1/leases/:id/egress/ticket endpoints used a 'resolveLease' function that only verified lease visibility rather than manageability. An attacker with 'use' (visibility-only) permissions can send a POST request to these endpoints to obtain bridge-agent tickets. These tickets allow the holder to connect to WebSocket routes and impersonate or replace trusted lease-side bridges, effectively gaining control over the lease's code, VNC, or egress traffic. The issue is fixed in version 0.12.0 by requiring owner, manage, or admin access for these endpoints.
Affected products
- openclaw Crabbox < 0.12.0
Timeline
- 2026-05-11: patched: Fix merged into main branch
- 2026-05-12: advisory: v0.12.0 release notes published
- 2026-05-14: disclosed: CVE-2026-8629 published