CVE-2026-75857: CodeWhale Exec_shell_interact Sends LLM-controlled Input To Vulnerability

HIGH
Advisory Identifier: GHSA-g29h-pfmp-qp9r
CVSS 7.0
CWE-269
Published
Advisory Summary

CVE-2026-75857 is a HIGH (CVSS 7.0) exec_shell_interact sends llm-controlled input to vulnerability (CWE-269: Improper Privilege Management) affecting CodeWhale libraries in the crates.io ecosystem. The issue involves exec_shell_interact sends llm-controlled input to a running shell without an approval prompt (privilege escalation). Remediation is available by upgrading affected packages to version 0.8.41, 0.8.64.

CVE-2026-75857 at a Glance

CVE Identifier CVE-2026-75857
GHSA Identifier GHSA-g29h-pfmp-qp9r
Severity HIGH
CVSS v3.1 Base Score 7.0
CWE Classification CWE-269: Improper Privilege Management
Affected Product CodeWhale
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 7.0

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H).

Attack Vector Local (AV:L)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-75857

To remediate this vulnerability, upgrade all affected CodeWhale dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

deepseek-tui fixed: Latest secure release
Upgrade deepseek-tui to Latest secure release
deepseek-tui fixed: 0.8.41
npm install deepseek-tui@0.8.41
codewhale-tui fixed: 0.8.64
Upgrade codewhale-tui to 0.8.64
codewhale fixed: 0.8.64
npm install codewhale@0.8.64
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for deepseek-tui

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-75857, inspect your project dependencies for CodeWhale:

inspect dependencies for deepseek-tui

Analyze the terminal output to locate any version of CodeWhale in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.8.41), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-269: Improper Privilege Management, where the product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. In CodeWhale, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Maintainer resolution The CodeWhale maintainers validated this report. The affected package ranges are recorded in the advisory metadata. Version 0.8.64 contains the fix in commit 57f3c89471e27ac4032d9791f6885e5d4408c381. Users should upgrade to 0.8.64 or later. The original reporter analysis is preserved below. ### Summary `exec_shell` is correctly approval-gated. Its sibling `exec_shell_interact` returns `ApprovalRequirement::Auto`, so when the model writes input into a shell the user already approved (a `python3 -i` REPL, `mysql`, `ssh`, `sudo -i`, etc.), no prompt fires. Inside those processes, "stdin" is the command surface, so the model gets to run commands at whatever privilege that process holds. The user approved opening the shell once, for a stated purpose; the input that then runs in it is chosen by the model, and can be steered by any prompt injection the agent ingests afterward. ### Details The vulnerability requires two ordinary preconditions: shell tools are enabled (the normal config for using CodeWhale as a coding agent), and the session already has one approved long-running interactive process. After that, any untrusted content the agent reads can drive a `exec_shell_interact` call. `crates/tui/src/tools/shell.rs:2834-2910`: ```rust fn capabilities(&self) -> Vec<ToolCapability> { vec![ToolCapability::ExecutesCode] } fn approval_requirement(&self) -> ApprovalRequirement { ApprovalRequirement::Auto // overrides the Required-for-ExecutesCode default } async fn execute(&self, input: Value, context: &ToolContext) -> Result<ToolResult, ToolError> { let task_id = required_task_id(&input)?; let close_stdin = optional_bool(&input, "close_stdin", false); let interaction_input = input .get("input").or_else(|| input.get("stdin")).or_else(|| input.get("data")) // LLM-controlled .and_then(serde_json::Value::as_str).unwrap_or(""); { let mut manager = context.shell_manager.lock()...; if !interaction_input.is_empty() || close_stdin { manager.write_stdin(task_id, interaction_input, close_stdin)...; // no prompt } } ... } ``` Same gate as the `rlm_eval` finding: the `Auto` at `approval_requirement()` makes `approval_required` false at `engine.rs:845`, so the `--approval-policy` is never consulted for the stdin write. The trait default at `spec.rs:632` would have been `Required`. The tool is registered unconditionally (`registry.rs:527`), and an alias `exec_interact` on the same struct is registered at `registry.rs:530`, so a fix must cover both names (it does, since they share `ShellInteractTool`). ### PoC 1. User asks the agent to open a REPL; the model calls `exec_shell command="python3 -i"`; the user sees and approves it once. 2. Later in the session, untrusted content (a fetched page, an MCP result, a repo `AGENTS.md`) instructs the model to send a payload to the open REPL. 3. The model calls `exec_shell_interact task_id=<repl> input="import os; os.system('...')\n"`. No prompt fires; Python runs it. Driving the interactive TUI through a pty and scanning the output for an approval dialog shows the only `Approval needed:` lines are for the initial `exec_shell`; `exec_shell_interact` never produces one, while a sentinel file proves the injected input ran. When the approved process is privileged, the reach scales with it: `mysql -u root` becomes arbitrary SQL, `ssh host` becomes commands on the remote host, `sudo -i` becomes root — none re-prompted. ### Impact Code or command execution inside an already-approved process, at that process's privilege level, with no prompt for the escalating input. Lower severity than the `rlm_eval` finding because it needs a prior user approval of an interactive shell, but higher reach when that shell is privileged. ### Credit [sai-sh](https://github.com/sai-sh)

CVE-2026-75857 Affected CodeWhale Versions

4 component(s)
Fixed Versions:
0.8.410.8.64
Product / Package Ecosystem Affected Versions Fixed Version
deepseek-tui
crates.io
≥ 0.3.10
≤ 0.8.41
deepseek-tui
npm
≥ 0.3.10
< 0.8.41
0.8.41
codewhale-tui
crates.io
≥ 0.8.41
< 0.8.64
0.8.64
codewhale
npm
≥ 0.8.41
< 0.8.64
0.8.64

References

Frequently Asked Questions

What is CVE-2026-75857?
CVE-2026-75857 is a security vulnerability in CodeWhale involving exec_shell_interact sends LLM-controlled input to a running shell without an approval prompt (privilege escalation) under CWE-269: Improper Privilege Management.
Which CodeWhale versions are affected?
Affected versions include releases prior to 0.8.41, 0.8.64 across affected packages: deepseek-tui, codewhale-tui, codewhale.
What version fixes CVE-2026-75857?
Upgrading to 0.8.41, 0.8.64 (or the latest patched release for your respective branch) resolves the vulnerability.
Is deepseek-tui affected?
Yes, deepseek-tui is affected in releases prior to Latest secure release, 0.8.41. Upgrade your dependency to Latest secure release, 0.8.41 or later.
Is codewhale-tui affected?
Yes, codewhale-tui is affected in releases prior to 0.8.64. Upgrade your dependency to 0.8.64 or later.
What is the CVSS score of CVE-2026-75857?
CVE-2026-75857 has a CVSS v3.1 base score of 7.0 (HIGH) with vector string CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-75857?
CVE-2026-75857 is classified under CWE-269: Improper Privilege Management (The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.).
How can I check crates.io dependencies for CVE-2026-75857?
Run the dependency tree command: 'inspect dependencies for deepseek-tui'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-g29h-pfmp-qp9r",
  "modified" : "2026-09-04T18:02:10Z",
  "published" : "2026-09-04T18:02:10Z",
  "aliases" : [ "CVE-2026-75857" ],
  "summary" : "CodeWhale: exec_shell_interact sends LLM-controlled input to a running shell without an approval prompt (privilege escalation)",
  "details" : "### Maintainer resolution\n\nThe CodeWhale maintainers validated this report. The affected package ranges are recorded in the advisory metadata. Version 0.8.64 contains the fix in commit 57f3c89471e27ac4032d9791f6885e5d4408c381. Users should upgrade to 0.8.64 or later. The original reporter analysis is preserved below.\n\n### Summary\n`exec_shell` is correctly approval-gated. Its sibling `exec_shell_interact` returns `ApprovalRequirement::Auto`, so when the model writes input into a shell the user already approved (a `python3 -i` REPL, `mysql`, `ssh`, `sudo -i`, etc.), no prompt fires. Inside those processes, \"stdin\" is the command surface, so the model gets to run commands at whatever privilege that process holds. The user approved opening the shell once, for a stated purpose; the input that then runs in it is chosen by the model, and can be steered by any prompt injection the agent ingests afterward.\n\n### Details\nThe vulnerability requires two ordinary preconditions: shell tools are enabled (the normal config for using CodeWhale as a coding agent), and the session already has one approved long-running interactive process. After that, any untrusted content the agent reads can drive a `exec_shell_interact` call.\n\n`crates/tui/src/tools/shell.rs:2834-2910`:\n\n```rust\nfn capabilities(&self) -> Vec<ToolCapability> {\n    vec![ToolCapability::ExecutesCode]\n}\n\nfn approval_requirement(&self) -> ApprovalRequirement {\n    ApprovalRequirement::Auto          // overrides the Required-for-ExecutesCode default\n}\n\nasync fn execute(&self, input: Value, context: &ToolContext) -> Result<ToolResult, ToolError> {\n    let task_id = required_task_id(&input)?;\n    let close_stdin = optional_bool(&input, \"close_stdin\", false);\n    let interaction_input = input\n        .get(\"input\").or_else(|| input.get(\"stdin\")).or_else(|| input.get(\"data\"))  // LLM-controlled\n        .and_then(serde_json::Value::as_str).unwrap_or(\"\");\n    {\n        let mut manager = context.shell_manager.lock()...;\n        if !interaction_input.is_empty() || close_stdin {\n            manager.write_stdin(task_id, interaction_input, close_stdin)...;          // no prompt\n        }\n    }\n    ...\n}\n```\n\nSame gate as the `rlm_eval` finding: the `Auto` at `approval_requirement()` makes `approval_required` false at `engine.rs:845`, so the `--approval-policy` is never consulted for the stdin write. The trait default at `spec.rs:632` would have been `Required`. The tool is registered unconditionally (`registry.rs:527`), and an alias `exec_interact` on the same struct is registered at `registry.rs:530`, so a fix must cover both names (it does, since they share `ShellInteractTool`).\n\n### PoC\n1. User asks the agent to open a REPL; the model calls `exec_shell command=\"python3 -i\"`; the user sees and approves it once.\n2. Later in the session, untrusted content (a fetched page, an MCP result, a repo `AGENTS.md`) instructs the model to send a payload to the open REPL.\n3. The model calls `exec_shell_interact task_id=<repl> input=\"import os; os.system('...')\\n\"`. No prompt fires; Python runs it.\n\nDriving the interactive TUI through a pty and scanning the output for an approval dialog shows the only `Approval needed:` lines are for the initial `exec_shell`; `exec_shell_interact` never produces one, while a sentinel file proves the injected input ran.\n\nWhen the approved process is privileged, the reach scales with it: `mysql -u root` becomes arbitrary SQL, `ssh host` becomes commands on the remote host, `sudo -i` becomes root — none re-prompted.\n\n### Impact\nCode or command execution inside an already-approved process, at that process's privilege level, with no prompt for the escalating input. Lower severity than the `rlm_eval` finding because it needs a prior user approval of an interactive shell, but higher reach when that shell is privileged.\n\n### Credit\n\n[sai-sh](https://github.com/sai-sh)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "deepseek-tui"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.3.10"
      }, {
        "last_affected" : "0.8.41"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "deepseek-tui"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.3.10"
      }, {
        "fixed" : "0.8.41"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "codewhale-tui"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.8.41"
      }, {
        "fixed" : "0.8.64"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "codewhale"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.8.41"
      }, {
        "fixed" : "0.8.64"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/Hmbown/CodeWhale/security/advisories/GHSA-g29h-pfmp-qp9r"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-75857"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Hmbown/CodeWhale/commit/57f3c89471e27ac4032d9791f6885e5d4408c381"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/Hmbown/CodeWhale"
  }, {
    "type" : "WEB",
    "url" : "https://www.vulncheck.com/advisories/codewhale-before-privilege-escalation-via-exec-shell-interact"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-269" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-04T18:02:10Z",
    "nvd_published_at" : "2026-08-18T16:18:21Z"
  }
}