CVE-2026-14738
6.3
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
Summary
A security flaw has been discovered in exo-explore exo up to 1.0.71. Affected is the function _image_cache_key of the file src/exo/worker/engines/mlx/vision.py of the component Vision Feature Cache. The manipulation results in use of weak hash. It is possible to launch the attack remotely. A high complexity level is associated with this attack. The exploitability is told to be difficult. The exploit has been released to the public and may be used for attacks. The pull request to fix this issue awaits acceptance.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| exo-explore | exo | 1.0.0 | affected |
| exo-explore | exo | 1.0.1 | affected |
| exo-explore | exo | 1.0.2 | affected |
| exo-explore | exo | 1.0.3 | affected |
| exo-explore | exo | 1.0.4 | affected |
| exo-explore | exo | 1.0.5 | affected |
| exo-explore | exo | 1.0.6 | affected |
| exo-explore | exo | 1.0.7 | affected |
| exo-explore | exo | 1.0.8 | affected |
| exo-explore | exo | 1.0.9 | affected |
| exo-explore | exo | 1.0.10 | affected |
| exo-explore | exo | 1.0.11 | affected |
| exo-explore | exo | 1.0.12 | affected |
| exo-explore | exo | 1.0.13 | affected |
| exo-explore | exo | 1.0.14 | affected |
| exo-explore | exo | 1.0.15 | affected |
| exo-explore | exo | 1.0.16 | affected |
| exo-explore | exo | 1.0.17 | affected |
| exo-explore | exo | 1.0.18 | affected |
| exo-explore | exo | 1.0.19 | affected |
| exo-explore | exo | 1.0.20 | affected |
| exo-explore | exo | 1.0.21 | affected |
| exo-explore | exo | 1.0.22 | affected |
| exo-explore | exo | 1.0.23 | affected |
| exo-explore | exo | 1.0.24 | affected |
| exo-explore | exo | 1.0.25 | affected |
| exo-explore | exo | 1.0.26 | affected |
| exo-explore | exo | 1.0.27 | affected |
| exo-explore | exo | 1.0.28 | affected |
| exo-explore | exo | 1.0.29 | affected |
| exo-explore | exo | 1.0.30 | affected |
| exo-explore | exo | 1.0.31 | affected |
| exo-explore | exo | 1.0.32 | affected |
| exo-explore | exo | 1.0.33 | affected |
| exo-explore | exo | 1.0.34 | affected |
| exo-explore | exo | 1.0.35 | affected |
| exo-explore | exo | 1.0.36 | affected |
| exo-explore | exo | 1.0.37 | affected |
| exo-explore | exo | 1.0.38 | affected |
| exo-explore | exo | 1.0.39 | affected |
| exo-explore | exo | 1.0.40 | affected |
| exo-explore | exo | 1.0.41 | affected |
| exo-explore | exo | 1.0.42 | affected |
| exo-explore | exo | 1.0.43 | affected |
| exo-explore | exo | 1.0.44 | affected |
| exo-explore | exo | 1.0.45 | affected |
| exo-explore | exo | 1.0.46 | affected |
| exo-explore | exo | 1.0.47 | affected |
| exo-explore | exo | 1.0.48 | affected |
| exo-explore | exo | 1.0.49 | affected |
| exo-explore | exo | 1.0.50 | affected |
| exo-explore | exo | 1.0.51 | affected |
| exo-explore | exo | 1.0.52 | affected |
| exo-explore | exo | 1.0.53 | affected |
| exo-explore | exo | 1.0.54 | affected |
| exo-explore | exo | 1.0.55 | affected |
| exo-explore | exo | 1.0.56 | affected |
| exo-explore | exo | 1.0.57 | affected |
| exo-explore | exo | 1.0.58 | affected |
| exo-explore | exo | 1.0.59 | affected |
| exo-explore | exo | 1.0.60 | affected |
| exo-explore | exo | 1.0.61 | affected |
| exo-explore | exo | 1.0.62 | affected |
| exo-explore | exo | 1.0.63 | affected |
| exo-explore | exo | 1.0.64 | affected |
| exo-explore | exo | 1.0.65 | affected |
| exo-explore | exo | 1.0.66 | affected |
| exo-explore | exo | 1.0.67 | affected |
| exo-explore | exo | 1.0.68 | affected |
| exo-explore | exo | 1.0.69 | affected |
| exo-explore | exo | 1.0.70 | affected |
| exo-explore | exo | 1.0.71 | affected |
Weaknesses
- CWE-328: Use of Weak Hash
- CWE-327: Risky Cryptographic Algorithm
References
- https://vuldb.com/vuln/376321
- https://vuldb.com/vuln/376321/cti
- https://vuldb.com/cve/CVE-2026-14738
- https://vuldb.com/submit/848737
- https://github.com/exo-explore/exo/issues/2151
- https://github.com/exo-explore/exo/pull/2152
- https://github.com/exo-explore/exo/
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.