Privilege escalation via visibility-only ticket minting
Published May 14, 2026 · Updated May 14, 2026
Authorization bypass in Crabbox before 0.12.0 allows remote authenticated users to impersonate trusted lease-side bridges. The Code, WebVNC, and Egress ticket handlers in worker/src/fleet.ts resolve leases with visibility-only authorization and mint bridge-agent tickets without requiring manage access. A valid account or token with use access to an enabled shared lease is sufficient to replace bridge state and compromise its traffic.
Summary
What happened
Authorization bypass in Crabbox before 0.12.0 allows remote authenticated users to impersonate trusted lease-side bridges. The Code, WebVNC, and Egress ticket handlers in worker/src/fleet.ts resolve leases with visibility-only authorization and mint bridge-agent tickets without requiring manage access. A valid account or token with use access to an enabled shared lease is sufficient to replace bridge state and compromise its traffic.
The record
- CVE
- CVE-2026-8629
- Published
- May 14, 2026
- Updated
- May 14, 2026
- Vendor
- OpenClaw Foundation
- Product
- Crabbox
- Classifications
- CWE-639, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 14, 2026CVE publishedPublication date reported by the CVE source.
- May 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.12.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Pull request 71 safe reproduction stepsproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo