# CVE-2026-8629: Crabbox < v0.12.0 Privilege Escalation via Agent Ticket Endpoints

> Users with visibility-only access can escalate privileges to obtain agent tickets and impersonate trusted bridges, potentially executing code.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/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:** No
- **Published:** 14 May 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-23m9-rr4p-xpwh

## What is CVE-2026-8629?

CVE-2026-8629 is a high-severity 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 a privilege escalation vulnerability that allows users with shared visibility-only access to obtain Code, WebVNC, and Egress agent tickets by sending POST requests to ticket endpoints. Attackers can exploit insufficient access control checks on the /v1/leases/:id/code/ticket, /v1/leases/:id/webvnc/ticket, and /v1/leases/:id/egress/ticket endpoints to obtain bridge-agent tickets and impersonate trusted lease-side bridges despite having only visibility permissions.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

No fix has been published for CVE-2026-8629 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-8629 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8629 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8629 is a high-severity 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8629 exists.

Affected product: openclaw crabbox. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-8629/ (Markdown: https://insights.sbomify.com/CVE-2026-8629/index.md)
```

## Sources

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

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