localGPT

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

Lifecycle evidence status

This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

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-5003	28 Mar 2026	4d41c7d1713b16b216d8e062e51a5dd88b20b054	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-5002	28 Mar 2026	4d41c7d1713b16b216d8e062e51a5dd88b20b054	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-5001	28 Mar 2026	4d41c7d1713b16b216d8e062e51a5dd88b20b054	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-5000	28 Mar 2026	4d41c7d1713b16b216d8e062e51a5dd88b20b054	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.