CodeWhale before version 0.8.64 does not validate file paths referenced in the project configuration's instructions field. A crafted .codewhale/config.toml in a repository can specify absolute or relative paths that point outside the expected workspace. When CodeWhale processes the repository, it reads those files and injects their contents into the AI prompt. This flaw lets an attacker read arbitrary filesystem locations, potentially exposing sensitive data and enabling further exfiltration or credential leakage.

Hmbown’s CodeWhale is affected for all releases prior to 0.8.64. Clients running any earlier version of the application are vulnerable to this file‑read issue. Based on the description, the flaw appears to be confined to the configuration instructions parsing component, with no other CodeWhale features reportedly impacted.

With a CVSS score of 8.7, the flaw carries a high severity rating. EPSS data is not available, but the attack requires delivering a malicious repository that contains a .codewhale/config.toml file. Based on the description, the likely attack vector involves a user or automated process cloning or importing a tainted repository into CodeWhale. Once processed, the attacker can read arbitrary files on the host of the CodeWhale instance, leading to confidentiality loss. The flaw is not listed in CISA’s KEV catalog, but based on patterns observed with similar file‑read flaws, zero‑day exploits can arise frequently, so vigilance is warranted.