CVE-2026-75912
Argument injection in CodeWhale git_blame allows arbitrary file reads.
Is CVE-2026-75912 being exploited?
Not confirmed. CVE-2026-75912 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.41% probability of exploitation in the next 30 days.
How severe is CVE-2026-75912?
CVE-2026-75912 is rated High with a CVSS score of 8.3. 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-75912?
Yes. A fix has been recorded for CVE-2026-75912. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-75912 affect?
CVE-2026-75912 affects CodeWhale < 0.8.64, CodeWhale git_blame tool. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-75912?
Upgrade to CodeWhale >=0.8.64, sanitize rev inputs, rotate any exposed keys.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unvalidated rev parameter lets attackers inject git options to read arbitrary files (e.g., SSH keys, credentials) and exfiltrate them via tool output.
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.