Intel

AIKIDO-2026-504584

lightrag-hku is vulnerable to Cache Poisoning

Cache PoisoningGHSA-597m-w632-p8qv Published Aug 3, 2026

65

Medium Risk

This Affects:

PYTHONlightrag-hku
0.0.1 - 1.5.4
Fixed in 1.5.5
Are you affected? Scan for Free

TL;DR

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.

Who does this affect?

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.

Background info

lightrag-hku is vulnerable to Cache Poisoning in versions 0.0.1 - 1.5.4.

How to fix this

Upgrade the lightrag-hku library to the patch version.

Are You Affected?

Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.

Free. No credit card required.

Aikido Platform