CVE-2026-75912

HIGHPre-NVD 7.47.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (37th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
7.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.4Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

CodeWhale versions before 0.8.64 contain an argument injection vulnerability in the git_blame tool that allows attackers to read arbitrary files by injecting git options into the unvalidated rev parameter. Attackers can supply rev values like --contents=/path/to/file to exfiltrate sensitive files such as SSH keys and credentials through the tool output returned to the model.

CVSS v3
7.4
EG Score
7.4HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity74% × 45%
The EG Score, 7.4 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
37th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 18, 2026

Last Modified

September 8, 2026

Advisory Details (3)

Auto-updated Aug 18, 2026
Patch available. Sources: github, github_commit.
Web page

CodeWhale before 0.8.64 Argument Injection via git_blame | Advisories | VulnCheck

https://www.vulncheck.com/advisories/codewhale-before-argument-injection-via-git-blame
GitHub commit

commit 9a34b5034d29 (Hmbown/CodeWhale)

Fix landed in Hmbown/CodeWhale commit 9a34b5034d29 — awaiting tagged release

https://github.com/Hmbown/CodeWhale/commit/9a34b5034d29f05d1f28fa61b04719ca6a741020
GitHub advisoryMentions a patch (unverified)

Argument Injection in `git_blame` Tool Allows Arbitrary File Read Without Approval · Advisory · Hmbown/CodeWhale · GitHub

https://github.com/Hmbown/CodeWhale/security/advisories/GHSA-c6mw-8xh8-gpq6

Vendor Advisories for CVE-2026-75912(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 2 ecosystems)
crates.io(2)
PackageVulnerable rangeFix by version rangeDependents
codewhale-tui—
  • 0.8.41 up to 0.8.64: fixed in 0.8.64
—
deepseek-tui—
  • 0.3.27 through 0.8.41: no fix on record
—
npm(2)
PackageVulnerable rangeFix by version rangeDependents
codewhale—
  • 0.8.41 up to 0.8.64: fixed in 0.8.64
—
deepseek-tui—
  • 0.3.27 up to 0.8.41: fixed in 0.8.41
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 53× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 99 is merged into the row it repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  2. 2026-10-13 07:15 UTCEG score recompute
  3. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  4. 2026-10-12 15:38 UTCEG score recompute
  5. 2026-10-11 19:24 UTCEG score recompute
  6. 2026-10-11 16:40 UTCEG score recompute
  7. 2026-10-11 13:59 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  11. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  13. 2026-10-06 19:31 UTCEG score recompute
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  15. 2026-10-06 08:24 UTCEG score recompute
  16. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  17. 2026-10-05 06:07 UTCEG score recompute
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  19. 2026-10-03 17:39 UTCEG score recompute
  20. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  21. 2026-10-03 02:46 UTCEG score recompute
  22. 2026-10-02 01:28 UTCEG score recompute
  23. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  24. 2026-09-30 20:57 UTCEG score recompute
  25. 2026-09-30 09:50 UTCEG score recompute
Show 73 more
  1. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  2. 2026-09-28 21:56 UTCEG score recompute
  3. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  4. 2026-09-27 19:04 UTCEG score recompute
  5. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  6. 2026-09-27 07:57 UTCEG score recompute
  7. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  8. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  9. 2026-09-25 01:29 UTCEG score recompute
  10. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  11. 2026-09-23 20:20 UTCEG score recompute
  12. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  13. 2026-09-22 20:27 UTCEG score recompute
  14. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  15. 2026-09-22 06:27 UTCEG score recompute
  16. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  17. 2026-09-20 20:47 UTCEG score recompute
  18. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  19. 2026-09-19 22:10 UTCEG score recompute
  20. 2026-09-18 21:51 UTCEG score recompute
  21. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  22. 2026-09-17 21:51 UTCEG score recompute
  23. 2026-09-16 21:57 UTCEG score recompute
  24. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  25. 2026-09-16 07:04 UTCEG score recompute
  26. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  27. 2026-09-15 08:46 UTCEG score recompute
  28. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  29. 2026-09-13 23:21 UTCEG score recompute
  30. 2026-09-13 01:07 UTCEG score recompute
  31. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  32. 2026-09-11 15:45 UTCEG score recompute
  33. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  34. 2026-09-10 17:25 UTCEG score recompute
  35. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  36. 2026-09-09 08:00 UTCEG score recompute
  37. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  38. 2026-09-06 15:44 UTCEG score recompute
  39. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  40. 2026-09-05 17:29 UTCEG score recompute
  41. 2026-09-04 19:01 UTCEG score recompute
  42. 2026-09-04 07:48 UTCEG score recompute
  43. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  44. 2026-09-02 21:57 UTCEG score recompute
  45. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  46. 2026-09-01 21:17 UTCEG score recompute
  47. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  48. 2026-08-31 00:32 UTCEG score recompute
  49. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  50. 2026-08-30 02:14 UTCEG score recompute
  51. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  52. 2026-08-29 03:58 UTCEG score recompute
  53. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  54. 2026-08-28 00:17 UTCEG score recompute
  55. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  56. 2026-08-27 01:52 UTCEG score recompute
  57. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  58. 2026-08-25 16:29 UTCEG score recompute
  59. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  60. 2026-08-24 18:08 UTCEG score recompute
  61. 2026-08-24 14:18 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  62. 2026-08-23 08:45 UTCEG score recompute
  63. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  64. 2026-08-22 10:30 UTCEG score recompute
  65. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  66. 2026-08-21 01:09 UTCEG score recompute
  67. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  68. 2026-08-20 02:37 UTCEG score recompute
  69. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  70. 2026-08-19 15:25 UTCEG score recompute
  71. 2026-08-18 16:33 UTCEG score recompute
  72. 2026-08-18 15:30 UTCEG score recomputeFirst assessed: 7.4 HIGH
  73. 2026-08-18 15:29 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-75912?
CVE-2026-75912 is a high-severity vulnerability; its CVE record was published on August 18, 2026. CodeWhale versions before 0.8.64 contain an argument injection vulnerability in the git_blame tool that allows attackers to read arbitrary files by injecting git options into the unvalidated rev parameter. Attackers can supply rev values like --contents=/path/to/file to exfiltrate sensitive files…
When was CVE-2026-75912 made public?
CVE-2026-75912 was made public on July 16, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 18, 2026. EchelonGraph's copy of the record carries a last-modified date of September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-75912 actively exploited?
CVE-2026-75912 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-75912?
CVE-2026-75912 has a CVSS base score of 7.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-75912?
A fix for CVE-2026-75912 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-75912 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-75912

Explore →

Is Your Infrastructure Affected by CVE-2026-75912?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs