Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY16 SECURITY RECORDS

The Eclipse Foundation

Eclipse Mosquitto

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

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2021-41039 1 Dec 2021 1.6 < unspecified; unspecified ≤ 2.0.11 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-34434 30 Aug 2021 2.0 < unspecified; unspecified ≤ 2.0.11 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-34432 27 Jul 2021 unspecified ≤ 2.0.7 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-34431 22 Jul 2021 1.6 < unspecified; unspecified ≤ 2.0.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-28166 7 Apr 2021 2.0 < unspecified; unspecified ≤ 2.0.9 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2019-11779 19 Sep 2019 1.5.0 to 1.6.5 inclusive No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-11778 18 Sep 2019 1.6.0 to 1.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7655 27 Mar 2019 1.0 < unspecified; unspecified ≤ 1.4.15 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-12551 27 Mar 2019 1.0 < unspecified; unspecified ≤ 1.5.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-12550 27 Mar 2019 1.0 < unspecified; unspecified ≤ 1.5.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-12546 27 Mar 2019 1.0 < unspecified; unspecified ≤ 1.5.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-12543 15 Nov 2018 1.5 < unspecified; unspecified ≤ 1.5.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7654 5 Jun 2018 unspecified ≤ 1.4.15 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2017-7653 5 Jun 2018 unspecified ≤ 1.4.15 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7652 25 Apr 2018 1.4.14 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2017-7651 24 Apr 2018 1.4.14 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗

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.