LightRAG

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

Official registry publication history is available at lightrag, but registry activity is not a publisher support boundary.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVE	Published	Affected versions	Fixed version information	Publisher evidence
CVE-2026-86062	22 Sep 2026	LightRAG: < 1.5.5	1.5.5.	Update reference ↗
CVE-2026-85740	22 Sep 2026	LightRAG: < 1.5.5	1.5.5.	Update reference ↗
CVE-2026-85734	22 Sep 2026	LightRAG: < 1.5.5	1.5.5.	Update reference ↗
CVE-2026-85725	22 Sep 2026	LightRAG: < 1.5.5	1.5.5.	Update reference ↗
CVE-2026-85709	22 Sep 2026	LightRAG: < 1.5.5	1.5.5.	Update reference ↗
CVE-2026-61808	7 Aug 2026	< 1.5.5rc1	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-61740	15 Jul 2026	< 1.5.4	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-61736	15 Jul 2026	< 1.5.4	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-39413	8 Apr 2026	< 1.4.14	No fixed version is explicitly recorded in the structured CVE data.	Update reference ↗
CVE-2025-6773	27 Jun 2025	1.3.0; 1.3.1; 1.3.2; 1.3.3; 1.3.4; 1.3.5; 1.3.6; 1.3.7	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.