# CVE-2026-85709: LightRAG: Sensitive Information Exposure Through Raw Exception Messages in API Error Responses

> Unauthenticated attackers can trigger errors to expose sensitive server configuration, database credentials, and internal paths via raw exception messages.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-hrmj-7rvj-4hg8, PYSEC-2026-4063

## What is CVE-2026-85709?

CVE-2026-85709 is a medium-severity vulnerability in HKUDS LightRAG, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LightRAG provides simple and fast retrieval-augmented generation. Prior to 1.5.5, the LightRAG API server returns raw Python exception text from error handlers in document_routes.py, graph_routes.py, query_routes.py, ollama_api.py, and lightrag_server.py. The detail=str(e), detail=str(exc), and equivalent formatted-message paths expose server filesystem paths, database host, port, user, and database names, language-model provider diagnostics, configuration details, and Python library internals to a network client that can trigger an error. The default unauthenticated configuration makes those responses reachable without credentials, and URI-configured backends can disclose connection strings containing credentials depending on the underlying driver error. This issue is fixed in version 1.5.5.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

## Which versions are affected by CVE-2026-85709?

3 open source packages ship an affected version, including lightrag-hku.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `lightrag-hku` | PyPI | All versions | 1.5.5 |
| `lightrag-hku` | PyPI | All versions | 1.5.5 |
| `lightrag-hku` | PyPI | All versions | 1.5.5 |

## How do I fix CVE-2026-85709?

Upgrade lightrag-hku to 1.5.5 or later.

## Is CVE-2026-85709 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85709 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85709 and fix it if it is affected.

What it is: CVE-2026-85709 is a medium-severity vulnerability in HKUDS LightRAG, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85709 exists.

Affected packages and fixed versions:
- lightrag-hku (PyPI): affected all versions; fixed in 1.5.5
- lightrag-hku (PyPI): affected all versions; fixed in 1.5.5
- lightrag-hku (PyPI): affected all versions; fixed in 1.5.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-85709/ (Markdown: https://insights.sbomify.com/CVE-2026-85709/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85709
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85709
- OSV: https://osv.dev/vulnerability/CVE-2026-85709

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-85709/
Summaries are generated and may contain mistakes; the official description above is the record.
