CVE-2026-10813: LMCache 16-bit Multimodal Hash Collision Vulnerability

lmcache Updated 18 Jul 2026

Summary

04/06/2026
No i
Low
3.6

CVE-2026-10813: LMCache: 16-bit multimodal hash collision can poison KV cache entries. Affects lmcache versions < 0.4.6. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

LMCache is a Python package available on PyPI that provides a key-value caching mechanism designed for efficient data retrieval and storage. It is widely used in applications requiring quick access to frequently used data. The package's functionality includes hashing and storing key-value pairs, but it has been found vulnerable to a specific flaw that can lead to cache poisoning.

Vulnerability Detail

A flaw has been identified in LMCache versions up to 0.4.6, specifically in the hex_hash_to_int16 function within the KV Cache Handler. This vulnerability allows an attacker to exploit a weak hash mechanism, potentially leading to cache poisoning. The attack must be executed locally and requires a high level of complexity, making it difficult to exploit. However, the existence of a published exploit indicates that it could be leveraged in targeted attacks, affecting the integrity of cached data.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary measure, users can implement additional validation checks on the input keys before they are processed by the caching mechanism to mitigate the risk of cache poisoning. However, this is not a complete fix and should only be used until the package is updated.

Conclusion

The LMCache vulnerability (CVE-2026-10813) poses a risk of cache poisoning due to a weak hash mechanism in versions up to 0.4.6. Users are advised to update to version 0.4.7 or later to mitigate this risk. Temporary workarounds can be implemented, but updating is the most effective solution.

See every vulnerability recorded for lmcache →

Share this vulnerability

FAQ

The CVSS score of this vulnerability is 3.6, indicating a low severity level.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

LMCache versions from 0.0.0 up to 0.4.6 are affected by this vulnerability.

Yes, an exploit has been published and may be used to target this vulnerability.

If an immediate update is not possible, consider implementing input validation as a temporary workaround to reduce the risk of exploitation.

Related vulnerabilities

Recent vulnerabilities recorded for lmcache.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback