AIKIDO-2026-398597
lightrag-hku is vulnerable to Observable Timing Discrepancy
59
CVE Score
Medium
Observable Timing Discrepancy
TL;DR
When plaintext passwords are stored in AUTH_ACCOUNTS, the verify_password function in lightrag/api/passwords.py compares the submitted password against the stored value with Python's == operator, which short-circuits on the first mismatched byte and is not constant-time. A client with low-latency access can measure the timing difference to recover the password length and characters one at a time, without triggering brute-force limits. This only affects deployments that store unhashed passwords rather than bcrypt hashes. The fix uses a constant-time comparison for plaintext passwords.
How do I fix this?
Upgrade the lightrag-hku library to the patch version.
Who does this affect?
You are affected if you are using a version that falls within the vulnerable range and you store unhashed plaintext passwords in AUTH_ACCOUNTS.
Package
Versions
0.0.1 - 1.5.4
Fixed in 1.5.5Background info
lightrag-hku is vulnerable to Observable Timing Discrepancy in versions 0.0.1 - 1.5.4.
Links
GitHub Release
Get secure today,
quickly and for free.
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 27001CompliantISO 42001Compliant
FedRAMPAuthorized© All Intel data is openly available and commercially licensed.