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

Apache Software Foundation

Apache IoTDB

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-2026-44630 10 Aug 2026 < 1.3.8; 2.0.0 < 2.0.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-40452 10 Jul 2026 1.3.5 < 1.3.8; 2.0.5 < 2.0.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-40009 10 Jul 2026 2.0.8 < 2.0.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-40008 10 Jul 2026 1.0.0 < 2.0.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-40007 10 Jul 2026 1.0.0 < 2.0.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-40006 10 Jul 2026 1.0.0 < 2.0.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-40005 10 Jul 2026 1.0.0 < 2.0.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-28564 10 Jul 2026 1.0.0 < 2.0.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-24013 6 Jul 2026 1.3.3 < 2.0.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-24012 6 Jul 2026 1.3.3 < 2.0.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-24014 6 Jul 2026 1.3.3 < 2.0.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-64152 26 Jun 2026 Apache IoTDB: 1.0.0 < 1.3.6, 2.0.0 < 2.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-55017 26 Jun 2026 Apache IoTDB: 2.0.0 < 2.0.6, 1.0.0 < 1.3.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-24713 9 Mar 2026 1.0.0 < 1.3.7; 2.0.0 < 2.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-24015 9 Mar 2026 1.0.0 < 1.3.7; 2.0.0 < 2.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-48392 24 Sep 2025 Apache IoTDB: 1.3.3 ≤ 1.3.4, 2.0.1-beta ≤ 2.0.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-48459 24 Sep 2025 Apache IoTDB: 1.0.0 < 2.0.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-26864 14 May 2025 0.10.0 ≤ 1.3.3; 2.0.1-beta < 2.0.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-24780 14 May 2025 1.0.0 < 1.3.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-46226 15 Jan 2024 1.0.0 ≤ 1.2.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-51656 21 Dec 2023 0.13.0 ≤ 0.13.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-24831 17 Apr 2023 0.13.0 ≤ 0.13.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-43766 26 Oct 2022 unspecified ≤ 0.13.2; 0.12.2 < unspecified No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-38370 5 Sep 2022 0.13.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-38369 5 Sep 2022 0.13.0 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.