CVE-2026-75911
Malicious repo config lets CodeWhale AI execute arbitrary shell commands.
Is CVE-2026-75911 being exploited?
Not confirmed. CVE-2026-75911 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.25% probability of exploitation in the next 30 days.
How severe is CVE-2026-75911?
CVE-2026-75911 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-75911?
Yes. A fix has been recorded for CVE-2026-75911. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-75911 affect?
CVE-2026-75911 affects CodeWhale < 0.8.64 (desktop/client), .codewhale/config.toml in project repositories. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-75911?
Upgrade to CodeWhale 0.8.64+; avoid opening untrusted repos.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Arbitrary shell command execution as the user when cloning/opening a poisoned repo; enables data theft, malware install, lateral movement.
Immediate action required
- affected>= 0.8.6 and < 0.8.41
- affected>= 0.8.41 and < 0.8.64
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.