LMCache up to 0.4.6 KV Cache utils.py hex_hash_to_int16 weak hash
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.3 | $0-$5k | 1.30 |
Summary
A vulnerability was found in LMCache up to 0.4.6. It has been classified as problematic. This vulnerability affects the function hex_hash_to_int16 of the file lmcache/integration/vllm/utils.py of the component KV Cache Handler. The manipulation leads to weak hash.
This vulnerability is documented as CVE-2026-10813. The attack needs to be performed locally. Additionally, an exploit exists.
The pull request to fix this issue awaits acceptance.
Details
A vulnerability was found in LMCache up to 0.4.6. It has been rated as problematic. This issue affects the function hex_hash_to_int16 of the file lmcache/integration/vllm/utils.py of the component KV Cache Handler. The manipulation with an unknown input leads to a weak hash vulnerability. Using CWE to declare the problem leads to 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). Impacted is integrity, and availability.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-10813. The exploitation is known to be difficult. An attack has to be approached locally. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.
The exploit is available 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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
Website
- Product: https://github.com/LMCache/LMCache/
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: 3301
Status: Not defined
Confirmation: 🔒
CVE: CVE-2026-10813 (🔒)
GCVE (CVE): GCVE-0-2026-10813
GCVE (VulDB): GCVE-100-368261
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 06/04/2026 07:39Changes: 06/04/2026 07:39 (58)
Complete: 🔍
Submitter: Dem00
Cache ID: 216::103
Submit
Accepted
- Submit #831641: LMCache 729ff73 Cache poisoning (by Dem00)
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.