Skip to content

← Actionable
Medium, CVSS 5.3amended

lightrag-hku: Sensitive Information Exposure Through Raw Exception Messages in API Error Responses

CVE-2026-85709GHSA-hrmj-7rvj-4hg8

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (lightrag-hku 1.5.5), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
  • CVE-2026-85709: 0.42% estimated exploitation activity in the next 30 days; percentile 36.29 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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): - documentroutes.py — 13 - graphroutes.py — 12 (mix of detail=f"...{str(e)}" and detail=errormsg) -…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-hrmj-7rvj-4hg8

  2. Revision 2 · amended ·

    Amended from osv record GHSA-hrmj-7rvj-4hg8

  3. Revision 1 · created ·

    Published from ghsa record GHSA-hrmj-7rvj-4hg8

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-85709

Advisory: lightrag-hku: Sensitive Information Exposure Through Raw Exception Messages in API Error Responses
IDs: CVE-2026-85709, GHSA-hrmj-7rvj-4hg8
Record: https://patchnext.com/advisories/cve-2026-85709 (revision 3, source checked 26 Oct 2026, 13:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: lightrag-hku 1.5.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI lightrag-hku: affected <= 1.5.4; fixed in 1.5.5

## Suggested inspection (read-only)
- `python -m pip show lightrag-hku`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on lightrag-hku.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-hrmj-7rvj-4hg8 (GitHub-reviewed advisory GHSA-hrmj-7rvj-4hg8 lists affected ranges: PyPI lightrag-hku >=0 <=1.5.4)
- Verified: https://osv.dev/vulnerability/GHSA-hrmj-7rvj-4hg8 (OSV record GHSA-hrmj-7rvj-4hg8 lists affected ranges: PyPI lightrag-hku >=0 <1.5.5 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…