{"answers":{"affected":"3 open source packages ship an affected version, including lightrag-hku.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85740 exists.","fix":"Upgrade lightrag-hku to 1.5.5 or later.","what":"CVE-2026-85740 is a high-severity server-side request forgery vulnerability in HKUDS LightRAG, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-85740 and fix it if it is affected.\n\nWhat it is: CVE-2026-85740 is a high-severity server-side request forgery vulnerability in HKUDS LightRAG, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85740 exists.\n\nAffected packages and fixed versions:\n- lightrag-hku (PyPI): affected all versions; fixed in 1.5.5\n- lightrag-hku (PyPI): affected all versions; fixed in 1.5.5\n- lightrag-hku (PyPI): affected all versions; fixed in 1.5.5\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-85740/ (Markdown: https://insights.sbomify.com/CVE-2026-85740/index.md)","id":"CVE-2026-85740","markdown":"https://insights.sbomify.com/CVE-2026-85740/index.md","name":"CVE-2026-85740","record":{"aliases":["GHSA-vv3m-f8x4-7377","PYSEC-2026-4064"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"LightRAG Python library","requires_auth":"low_privilege","summary":"Attackers can bypass SSRF guards using IPv6 transition addresses to access internal resources in LightRAG deployments with NAT64/DNS64 routing.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"lightrag-hku: SSRF via IPv6-transition address bypass (NAT64, IPv4-compatible, 6to4) of the native-markdown image-download guard","id":"CVE-2026-85740","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":3,"n_references":6,"next":{"headline":"MariaDB: Out-of-bound buffer read on in `ST_Area` of a multipolygon.","id":"CVE-2026-85745"},"packages":[{"ecosystem":"PyPI","fixed":["1.5.5"],"introduced":["0"],"last_affected":[],"package":"lightrag-hku","purl":null,"source":"GHSA-vv3m-f8x4-7377"},{"ecosystem":"PyPI","fixed":["1.5.5"],"introduced":["0"],"last_affected":[],"package":"lightrag-hku","purl":"pkg:pypi/lightrag-hku","source":"GHSA-vv3m-f8x4-7377"},{"ecosystem":"PyPI","fixed":["1.5.5"],"introduced":["0"],"last_affected":[],"package":"lightrag-hku","purl":"pkg:pypi/lightrag-hku","source":"PYSEC-2026-4064"}],"prev":{"headline":"TREK: SSRF Guard Bypass via IPv6 Transition Addresses (NAT64/6to4)","id":"CVE-2026-85738"},"products":["LightRAG"],"published":"2026-09-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-28","vendors":["HKUDS"]},"summary":"Attackers can bypass SSRF guards using IPv6 transition addresses to access internal resources in LightRAG deployments with NAT64/DNS64 routing.","url":"https://insights.sbomify.com/CVE-2026-85740/"}