CVE-2026-75913
Argument injection in CodeWhale git_show allows arbitrary file write by invoking user.
Is CVE-2026-75913 being exploited?
Not confirmed. CVE-2026-75913 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.33% probability of exploitation in the next 30 days.
How severe is CVE-2026-75913?
CVE-2026-75913 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-75913?
Yes. A fix has been recorded for CVE-2026-75913. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-75913 affect?
CVE-2026-75913 affects CodeWhale (codewhale-tui) >=0.8.41 <0.8.64, git_show tool, Developer workstations and CI runners invoking CodeWhale. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-75913?
Upgrade to CodeWhale 0.8.64+, validate repos and audit sensitive files (~/.ssh, ~/.bashrc).
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Malicious repo + prompt injection causes unprompted arbitrary file write as invoking user (e.g., ~/.ssh/authorized_keys), enabling persistence or account takeover.
Immediate action required
- affected>= 0.3.27 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.