Skip to main content
VulnerabilityPublished Updated

CVE-2026-85740: HKUDS LightRAG · Server-Side Request Forgery (SSRF)

Affects HKUDS LightRAGSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 1.5.5 soon.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.5.5
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade LightRAG and hkuds/LightRAG to 1.5.5.

Affected software

ProductAffectedFixed in
HKUDSLightRAGAffected
  • <1.5.5
Fixed in
  • 1.5.5
GitHubhkuds/LightRAGpkg:github/hkuds/LightRAGOther threatsAffected
  • <1.5.5
Fixed in
  • 1.5.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to LightRAG version 1.5.5 or later, where this SSRF vulnerability is fixed. The fix improves address validation to correctly handle IPv4 addresses embedded in IPv6 transition wrappers, preventing unauthorized internal resource fetching. No other mitigation is indicated or necessary if the upgrade is applied.

Description

LightRAG provides simple and fast retrieval-augmented generation. Prior to 1.5.5, _validated_addresses in lightrag/parser/markdown/parser.py evaluates the literal resolved address with ipaddress.is_global without consistently classifying an IPv4 address embedded in an IPv6 transition wrapper. A caller who can upload a Markdown or textpack document can supply an external image URL using NAT64 64:ff9b::/96 or an IPv4-compatible form that embeds a loopback, private, or cloud-metadata IPv4 address. On a deployment with compatible NAT64 or DNS64 routing, _download and _build_guarded_opener accept the wrapper and fetch the internal resource, whose body is then ingested. Current interpreter behavior already blocks some RFC 8215 and 6to4 forms, but the fixed guard handles all documented wrappers without becoming more permissive than the standard library. This issue is fixed in version 1.5.5.

References

Community reviews

Loading reviews…