Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-85709 medium CVSS 5.3

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

Summary

Vulnerability in lightrag-hku (CVE-2026-85709). Risk of unauthorized operations or information disclosure. Exploitable via main. Mitigation: upgrade to 1.5.5 or later.

Original description

The description as published by the source.

Summary

The LightRAG API server passes raw Python exception messages directly into HTTP
error responses across 30+ error handlers in every router. When combined with
the default unauthenticated configuration (see companion report on CWE-306), any
network-reachable client can trigger exceptions whose raw text discloses
internal infrastructure — server filesystem paths, database host/port/user, LLM
provider error details, and Python library internals. No global exception
handler sanitizes error messages before they reach the client.

Details

Throughout the API route handlers, exceptions are caught and their string
representation is returned verbatim via detail=str(e) / detail=str(exc)
(and f-string variants such as detail=f"...: {str(e)}"). This occurs in every
router file. Location breakdown on the current main branch:

HTTP 500 — raw exception passthrough (except Exception as e):

  • document_routes.py — 13
  • graph_routes.py — 12 (mix of detail=f"...{str(e)}" and detail=error_msg)
  • query_routes.py — 3
  • ollama_api.py — 2
  • lightrag_server.py — 1 (health endpoint)

HTTP 422 — raw exception passthrough (except ValueError as exc):

  • document_routes.py — 2 (chunking-config validation)

Total: ~33 raw-exception-to-HTTP-response locations. The only pre-existing
custom exception handler in lightrag_server.py is specific to
RequestValidationError for /query/data; it does not cover the generic
Exception handlers in route code.…

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-85709 has been found in lightrag-hku.
Attackers can target a specific entry point like main over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/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-85709" on the vendor's site.

CVE-2026-85709 (lightrag-hku) — CWE-209 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: main / document_routes.py / graph_routes.py / query_routes.py
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-209) exists in lightrag-hku. Attackers reach the vulnerable code path via main without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of lightrag-hku. Attack surface: main / document_routes.py / graph_routes.py / query_routes.py.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.

🔧 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 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

  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
    Apply patch patch 
    Upgrade lightrag-hku to 1.5.5

    ステージング環境で 1.5.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

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

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