# CVE-2026-9565: haojing8312 WorkClaw Blacklist bash.rs is_dangerous os command injection

> Remote attackers can execute arbitrary OS commands via the bash tool's blacklist handler in WorkClaw, requiring immediate attention from users.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 26 May 2026
- **Updated:** 28 May 2026
- **Also known as:** GHSA-h75h-m8wx-2x9c

## What is CVE-2026-9565?

CVE-2026-9565 is a medium-severity command injection vulnerability in haojing8312 WorkClaw, published on 26 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was determined in haojing8312 WorkClaw up to 0.6.4. This affects the function is_dangerous of the file apps/runtime/src-tauri/src/agent/tools/bash.rs of the component Blacklist Handler. Executing a manipulation can lead to os command injection. The attack can be executed remotely. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

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


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

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

## Is CVE-2026-9565 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9565 is a medium-severity command injection vulnerability in haojing8312 WorkClaw, published on 26 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-9565 exists.

Affected product: haojing8312 WorkClaw. 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-9565/ (Markdown: https://insights.sbomify.com/CVE-2026-9565/index.md)
```

## Sources

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

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