CVE
CodeWhale remote command execution in shell approval logic
CodeWhale 0.8.67 and earlier are affected in the default interactive Agent profile. Fixed in 0.9.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- Exploited
- No known exploitation
- Fix
- Fixed in 0.9.0
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 31/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
CodeWhale, a terminal coding agent, can be made to run arbitrary programs on the developer's host because its command-approval logic wrongly treated certain search commands with exec flags as read-only and auto-approved them. Attacker-controlled content that influences an agent tool call can reach this remotely, without logging in and without any user action, and the flaw can lead to unauthorized access, modification, or disruption.
Original description
CodeWhale is a DeepSeek and MiMo coding agent for the terminal. Prior to 0.9.0, the ExecShellTool::approval_requirement_for path used is_parallel_readonly_command to downgrade commands to automatic approval based on a flag-stripped command allowlist. The allowlist treated fd, rg, and git grep as read-only even when fd -x or fd --exec, rg --pre, or git grep --open-files-in-pager selected an external program. registered_tool_approval_required returned without displaying a prompt for that automatic classification, and the later command-safety check also treated the base utilities as safe. Attacker-controlled content that influenced an agent tool call could therefore cause arbitrary program execution on the developer host without the approval promised by the default interactive profile, resulting in unauthorized access, modification, or disruption. This issue is fixed in version 0.9.0.
Who should check
Developers running CodeWhale 0.8.67 or earlier, via the codewhale npm package or codewhale-tui crate, using the default interactive Agent profile.
“CodeWhale 0.8.67 and earlier are affected.”
cve.now Index
- Exploitation0/40No signal
- Exposure22/25Default setups, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.1/10CVSS 8.1, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: 0.9.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-83816 (CodeWhale: exec_shell parallel-readonly classifier auto-approves fd/rg/git grep exec flags enabling silent RCE), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-83816 (entry last updated 2026-11-16):
Affected:
- codewhale-hq CodeWhale: fixed in 0.9.0
Fixed versions: 0.9.0.
Conditions (all must be true for the bug to be hit):
- Affected CodeWhale versions are 0.8.67 and earlier. (source: https://github.com/codewhale-hq/Codewhale/security/advisories/GHSA-3mgh-93r5-r7jf)
- The interactive Agent profile is in use, which is the default profile. (source: https://github.com/codewhale-hq/Codewhale/security/advisories/GHSA-3mgh-93r5-r7jf)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-83816 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-83816 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/codewhale-hq/Codewhale/security/advisories/GHSA-3mgh-93r5-r7jf
- https://github.com/codewhale-hq/Codewhale/commit/208421b9d23d81cea3311a1eeb2a2ea81d637686
- https://github.com/codewhale-hq/Codewhale/releases/tag/v0.9.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-83816
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-83816"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- codewhale-hq CodeWhale
fixed in 0.9.0
Evidence 5
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 2
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-83816
Is CVE-2026-83816 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The exec_shell parallel-readonly classifier automatically approves exec flags of fd, rg, and git grep. This lets an attacker run arbitrary external programs, with any arguments, on the developer host with no approval prompt.Source: github.com
Which versions are affected by CVE-2026-83816?
CodeWhale: before 0.9.0.Source: cve.now feed data
Am I affected, and how do I check?
CodeWhale 0.8.67 and earlier are affected, in the interactive Agent profile, which is the default profile. To check a setup, look at the installed CodeWhale version and whether the interactive Agent profile is in use.Source: github.com
How do I fix CVE-2026-83816?
Upgrade CodeWhale to 0.9.0, the fixed version listed for this vulnerability.Source: github.com