CVE-2026-75911

What it is

CodeWhale versions before 0.8.64 fail to properly validate the allow_shell configuration parameter from project config files, allowing attackers to enable arbitrary shell command execution by committing a malicious .codewhale/config.toml file to a repository. When a user clones and opens the repository in CodeWhale, the AI model gains access to exec_shell and task_shell tools, enabling execution of arbitrary shell commands on the victim's machine without explicit user consent.

At a glance

Exploitability

Can be exploited locally on the machine without logging in, but needs a user to act. High risk of data exposure, data tampering, service disruption.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-08-18 16:18 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-22 22:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.2% in the next 30 days (EPSS).
• Severity: 8.5 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-08-18 16:18 UTC

Last modified

2026-10-22 22:10 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-94 · Code injection

Record status

Deferred

Attack profile CVSS 4.0 · 8.5

Attack vector

Local

Complexity

Low

Attack requirements

None

Privileges needed

None

User interaction

Passive

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-75911.md and follow it. Check whether this project is affected by CVE-2026-75911. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge