CVE-2026-75914

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (43rd 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
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

CodeWhale versions before 0.8.64 contain a path traversal vulnerability in the image_analyze tool that fails to canonicalize symlinks before reading files. Attackers can create workspace symlinks pointing to external files with image extensions to leak file bytes to the vision endpoint without user approval.

CVSS v3
7.5
EG Score
7.5HIGHmedium 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)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
43rd
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 Path Traversal via image_analyze symlink | Advisories | VulnCheck

https://www.vulncheck.com/advisories/codewhale-before-path-traversal-via-image-analyze-symlink
GitHub commit

commit 26de44a8bd50 (Hmbown/CodeWhale)

Fix landed in Hmbown/CodeWhale commit 26de44a8bd50 — awaiting tagged release

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

image_analyze follows workspace symlinks, leaking external file bytes · Advisory · Hmbown/CodeWhale · GitHub

https://github.com/Hmbown/CodeWhale/security/advisories/GHSA-w7wx-5q49-r59w

Vendor Advisories for CVE-2026-75914(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.8.32 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.8.32 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.

Showing the most recent 98 of 103 refreshes on record for this CVE.

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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 5 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-75914?
CVE-2026-75914 is a high-severity vulnerability; its CVE record was published on August 18, 2026. CodeWhale versions before 0.8.64 contain a path traversal vulnerability in the image_analyze tool that fails to canonicalize symlinks before reading files. Attackers can create workspace symlinks pointing to external files with image extensions to leak file bytes to the vision endpoint without user…
When was CVE-2026-75914 made public?
CVE-2026-75914 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-75914 actively exploited?
CVE-2026-75914 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-75914?
CVE-2026-75914 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-75914?
A fix for CVE-2026-75914 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-75914 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-75914

Explore →

Is Your Infrastructure Affected by CVE-2026-75914?

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

Book a Demo →Browse All CVEs