exo-explore exo up to 1.0.71 Vision Feature Cache vision.py _image_cache_key weak hash

Summaryinfo

A vulnerability, which was classified as problematic, has been found in exo-explore exo up to 1.0.71. Affected by this vulnerability is the function _image_cache_key of the file src/exo/worker/engines/mlx/vision.py of the component Vision Feature Cache. This manipulation causes weak hash. This vulnerability is handled as CVE-2026-14738. The attack can be initiated remotely. Additionally, an exploit exists. The pull request to fix this issue awaits acceptance.

Detailsinfo

A vulnerability has been found in exo-explore exo up to 1.0.71 and classified as problematic. Affected by this vulnerability is the function _image_cache_key of the file src/exo/worker/engines/mlx/vision.py of the component Vision Feature Cache. The manipulation with an unknown input leads to a weak hash vulnerability. The CWE definition for the vulnerability is CWE-328. The product uses an algorithm that produces a digest (output value) that does not meet security expectations for a hash function that allows an adversary to reasonably determine the original input (preimage attack), find another input that can produce the same hash (2nd preimage attack), or find multiple inputs that evaluate to the same hash (birthday attack). As an impact it is known to affect confidentiality.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-14738. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.

It is possible to download the exploit at github.com. It is declared as proof-of-concept. The pull request to fix this issue awaits acceptance.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• exo-explore

Name

• exo

Version

• 1.0.0
• 1.0.1
• 1.0.2
• 1.0.3
• 1.0.4
• 1.0.5
• 1.0.6
• 1.0.7
• 1.0.8
• 1.0.9
• 1.0.10
• 1.0.11
• 1.0.12
• 1.0.13
• 1.0.14
• 1.0.15
• 1.0.16
• 1.0.17
• 1.0.18
• 1.0.19
• 1.0.20
• 1.0.21
• 1.0.22
• 1.0.23
• 1.0.24
• 1.0.25
• 1.0.26
• 1.0.27
• 1.0.28
• 1.0.29
• 1.0.30
• 1.0.31
• 1.0.32
• 1.0.33
• 1.0.34
• 1.0.35
• 1.0.36
• 1.0.37
• 1.0.38
• 1.0.39
• 1.0.40
• 1.0.41
• 1.0.42
• 1.0.43
• 1.0.44
• 1.0.45
• 1.0.46
• 1.0.47
• 1.0.48
• 1.0.49
• 1.0.50
• 1.0.51
• 1.0.52
• 1.0.53
• 1.0.54
• 1.0.55
• 1.0.56
• 1.0.57
• 1.0.58
• 1.0.59
• 1.0.60
• 1.0.61
• 1.0.62
• 1.0.63
• 1.0.64
• 1.0.65
• 1.0.66
• 1.0.67
• 1.0.68
• 1.0.69
• 1.0.70
• 1.0.71

Website

• Product: https://github.com/exo-explore/exo/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Submitinfo

Accepted

• Submit #848737: exo-explore exo 1.0.71 Use of Weak Hash (by Dem0)

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion