lightrag-hku is vulnerable to Cache Poisoning
65
CVE Score
Medium
Cache Poisoning
LightRAG caches generated query answers under a key computed over the query text, mode, retrieval parameters, and LLM identity, but omits conversation_history from that key even though it is passed to the model and materially changes the answer. A caller who supplies conversation_history can therefore determine the answer stored for a given question, and that stored answer is later returned verbatim to callers who supply no history. Because the default whitelist exempts the Ollama-compatible /api/chat route, the writing caller can be unauthenticated while the reading caller is authenticated, and the poisoned answer is served alongside genuine references. The fix bypasses the query-answer cache for both read and write whenever conversation_history is non-empty.
Upgrade the lightrag-hku library to the patch version.
You are affected if you are using a version that falls within the vulnerable range and clients can send conversation_history on query or chat requests against a shared response cache.
0.0.1 - 1.5.4
Fixed in 1.5.5lightrag-hku is vulnerable to Cache Poisoning in versions 0.0.1 - 1.5.4.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.