zilliztech GPTCache up to 0.1.44 Cache Key pre.py BufferedReader.peek input_data["image"] weak hash
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.3 | $0-$5k | 1.30 |
Summary
A vulnerability was found in zilliztech GPTCache up to 0.1.44 and classified as problematic. This affects the function BufferedReader.peek of the file gptcache/processor/pre.py of the component Cache Key Handler. Executing a manipulation of the argument input_data["image"] can lead to weak hash.
This vulnerability is registered as CVE-2026-10812. The attack needs to be launched locally. Furthermore, an exploit is available.
The pull request to fix this issue awaits acceptance.
Details
A vulnerability was found in zilliztech GPTCache up to 0.1.44. It has been declared as problematic. This vulnerability affects the function BufferedReader.peek of the file gptcache/processor/pre.py of the component Cache Key Handler. The manipulation of the argument input_data["image"] 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 integrity, and availability.
The advisory is shared for download at github.com. This vulnerability was named CVE-2026-10812. The exploitation appears to be difficult. The attack needs to be approached locally. Technical details and also a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1600.001.
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.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
- 0.1.0
- 0.1.1
- 0.1.2
- 0.1.3
- 0.1.4
- 0.1.5
- 0.1.6
- 0.1.7
- 0.1.8
- 0.1.9
- 0.1.10
- 0.1.11
- 0.1.12
- 0.1.13
- 0.1.14
- 0.1.15
- 0.1.16
- 0.1.17
- 0.1.18
- 0.1.19
- 0.1.20
- 0.1.21
- 0.1.22
- 0.1.23
- 0.1.24
- 0.1.25
- 0.1.26
- 0.1.27
- 0.1.28
- 0.1.29
- 0.1.30
- 0.1.31
- 0.1.32
- 0.1.33
- 0.1.34
- 0.1.35
- 0.1.36
- 0.1.37
- 0.1.38
- 0.1.39
- 0.1.40
- 0.1.41
- 0.1.42
- 0.1.43
- 0.1.44
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.6VulDB Meta Temp Score: 3.3
VulDB Base Score: 3.6
VulDB Temp Score: 3.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Weak hashCWE: CWE-328 / CWE-327 / CWE-310
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
06/04/2026 Advisory disclosed06/04/2026 VulDB entry created
06/04/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 684
Status: Not defined
Confirmation: 🔒
CVE: CVE-2026-10812 (🔒)
GCVE (CVE): GCVE-0-2026-10812
GCVE (VulDB): GCVE-100-368260
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 06/04/2026 07:28Changes: 06/04/2026 07:28 (60)
Complete: 🔍
Submitter: Dem0
Cache ID: 216::103
Submit
Accepted
- Submit #831636: zilliztech GPTCache 0.1.44 Cache poisoning / improper cache key generation (by Dem0)
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.