CVE-2026-9565
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA command injection vulnerability exists in the is_dangerous function within apps/runtime/src-tauri/src/agent/tools/bash.rs of the WorkClaw project (versions up to 0.6.4). The Blacklist Handler component fails to properly sanitize inputs, allowing an attacker to inject malicious OS commands remotely.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if WorkClaw application is installedSearch for WorkClaw in installed applications or check for the presence of the application directory (typically under Program Files, /opt, or the user's home directory). Look for executable files named 'workclaw' or related binaries.Affected if WorkClaw application is present on the system
-
Locate the vulnerable bash.rs fileNavigate to the source or installation directory and look for the path apps/runtime/src-tauri/src/agent/tools/bash.rs. If this file exists, the component is present.Affected if The file apps/runtime/src-tauri/src/agent/tools/bash.rs exists in the installation or source directory
-
Verify the is_dangerous function existsOpen bash.rs and search for the function named 'is_dangerous'. This function handles blacklist validation for the blacklist handler.Affected if The is_dangerous function is found in the bash.rs file
-
Check if blacklist handler is enabled or in useReview the application configuration files (look for config.json, settings.toml, or similar) to determine if the blacklist validation feature is actively enabled. Check runtime logs for references to blacklist or is_dangerous function calls.Affected if The blacklist handler feature is enabled or appears in active use
-
Determine installed version for comparisonCheck the application's version by running 'workclaw --version' or inspecting metadata files like Cargo.toml, package.json, or VERSION files in the installation directory.Affected if The installed version cannot be determined or falls within an unknown affected range (no patch available)
A user is affected if the WorkClaw application is installed, the vulnerable bash.rs file with the is_dangerous function exists, and the blacklist handler feature is enabled or in use.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation and sanitization in the is_dangerous function's blacklist handler; avoid using user-controlled input in shell command execution. Consider applying the latest security patches or contacting the vendor for an official fix.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9565 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-9565 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data