CodeWhale before 0.8.64 Arbitrary File Read via instructions
Hmbown CodeWhale
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| deepseek-tui crates.io |
| No fix yet |
| deepseek-tui npm |
|
|
| codewhale-tui crates.io |
|
Hmbown CodeWhale
| Product | Affected | Fixed in |
|---|---|---|
| deepseek-tui crates.io |
| No fix yet |
| deepseek-tui npm |
|
|
| codewhale-tui crates.io |
|
|
| codewhale npm |
|
|
CodeWhale versions before 0.8.64 fail to validate file paths in the project config instructions field, allowing attackers to read arbitrary files on the victim's system. A malicious .codewhale/config.toml file in a cloned repository can specify paths outside the workspace that are read and injected into the AI system prompt for exfiltration.
From the CVE record · VulnCheck
CodeWhale does not validate paths in the project config instructions field. If a user clones a repository containing a malicious .codewhale/config.toml file, an attacker can cause files outside the workspace to be read and injected into the AI system prompt for exfiltration.
Check installations of crates.io deepseek-tui >=0.8.8, npm deepseek-tui >=0.8.8 <0.8.41, crates.io codewhale-tui >=0.8.41 <0.8.64, or npm codewhale >=0.8.41 <0.8.64.