deepseek-harness

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 deepseek-harness, 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-101132	28 Sep 2026	deepseek-harness: 0.1.7-rc.0, 0.1.7-rc.1, 0.1.7-rc.2	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-82533	8 Sep 2026	< 0.1.2-alpha.1	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.