CVE-2026-75859 Hmbown CVE debrief

Who should care

Defenders responsible for CodeWhale deployments, security teams, and operators should assess exposure and prioritize verification of the version in use. This includes reviewing system logs for suspicious activity, verifying the integrity of the config.toml file, and upgrading to version 0.8.64 or later. Additionally, vulnerability management and platform security teams should be aware of the potential impact and take necessary precautions to prevent exfil

Why it matters

CVE-2026-75859 is a high-severity vulnerability in CodeWhale versions before 0.8.64, allowing attackers to read arbitrary files on the victim's system. Defenders responsible for CodeWhale deployments should assess exposure and prioritize verification of the version in use.

• Verify the integrity of the config.toml file to prevent exfiltration
• Monitor system logs for suspicious activity related to CodeWhale
• Upgrade to version 0.8.64 or later to patch the vulnerability

Technical summary

The vulnerability is caused by a lack of validation in the project config instructions field, allowing attackers to specify paths outside the workspace that are read and injected into the AI system for exfiltration. This issue affects CodeWhale versions before 0.8.64, where a malicious .codewhale/config.toml file in a cloned repository can be used to read arbitrary files on the victim's system. The vulnerability has a high severity, with a CVSS score of 8.7, and defenders should prioritize verifying the version of CodeWhale in use and upgrading to version 0.8.64 or later.

Defensive priority

Defenders should prioritize verifying the version of CodeWhale in use and upgrading to version 0.8.64 or later. Additionally, defenders should be cautious when cloning repositories and verify the integrity of the config.toml file.

Recommended defensive actions

• Verify the version of CodeWhale in use and upgrade to version 0.8.64 or later
• Be cautious when cloning repositories and verify the integrity of the config.toml file
• Monitor system logs for suspicious activity related to CodeWhale
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD vulnerability detail page provide information on the vulnerability. However, the exact scope of affected versions and systems requires further verification. Affected CodeWhale versions before 0.8.64 may be vulnerable, but specific configurations and environments need assessment. Defenders should verify the version in use, review system logs, and assess exposure to potential file path manipulation attacks.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.