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

ArcadeData

arcadedb

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-93598 18 Sep 2026 arcadedb: < 26.9.1 arcadedb: 26.9.1 Update reference ↗
CVE-2026-93597 18 Sep 2026 arcadedb: < 26.9.1 arcadedb: 26.9.1 Update reference ↗
CVE-2026-93596 18 Sep 2026 arcadedb: < 26.9.1 arcadedb: 26.9.1 Update reference ↗
CVE-2026-93595 18 Sep 2026 arcadedb: < 26.9.1 arcadedb: 26.9.1 Update reference ↗
CVE-2026-93594 18 Sep 2026 arcadedb: < 26.9.1 arcadedb: 26.9.1 Update reference ↗
CVE-2026-93593 18 Sep 2026 arcadedb: < 26.9.1 arcadedb: 26.9.1 Update reference ↗
CVE-2026-65831 15 Sep 2026 arcadedb: < 26.7.1; arcadedb-server: < 26.7.1 26.7.1. Update reference ↗
CVE-2026-54077 15 Sep 2026 arcadedb: < 26.6.1; arcadedb-engine: < 26.6.1 26.6.1. Update reference ↗
CVE-2026-54076 15 Sep 2026 arcadedb: < 26.6.1; arcadedb-engine: < 26.6.1 26.6.1. Update reference ↗
CVE-2026-76225 19 Aug 2026 < 26.8.1 26.8.1 Update reference ↗
CVE-2026-76224 19 Aug 2026 < 26.8.1 26.8.1 Update reference ↗
CVE-2026-76223 19 Aug 2026 < 26.8.1 26.8.1 Update reference ↗
CVE-2026-75855 18 Aug 2026 < 26.8.1 26.8.1 Update reference ↗
CVE-2026-75854 18 Aug 2026 arcadedb: < 26.8.1 arcadedb: 26.8.1 Update reference ↗
CVE-2026-75853 18 Aug 2026 < 26.8.1 26.8.1 Update reference ↗
CVE-2026-75852 18 Aug 2026 < 26.8.1 26.8.1 Update reference ↗
CVE-2026-75851 18 Aug 2026 < 26.8.1 26.8.1 Update reference ↗
CVE-2026-75850 18 Aug 2026 < 26.8.1 26.8.1 Update reference ↗
CVE-2026-75846 18 Aug 2026 < 26.8.1 26.8.1 Update reference ↗
CVE-2026-75845 18 Aug 2026 26.4.2 < 26.8.1 26.8.1 Update reference ↗
CVE-2026-75844 18 Aug 2026 < 26.8.1 26.8.1 Update reference ↗
CVE-2026-75843 18 Aug 2026 < 26.8.1 26.8.1 Update reference ↗
CVE-2026-75842 18 Aug 2026 < 26.8.1 26.8.1 Update reference ↗
CVE-2026-75841 18 Aug 2026 < 26.8.1 26.8.1 Update reference ↗
CVE-2026-75840 18 Aug 2026 < 26.8.1 26.8.1 Update reference ↗
CVE-2026-75839 18 Aug 2026 < 26.8.1 26.8.1 Update reference ↗
CVE-2026-68578 2 Aug 2026 < 26.7.3 26.7.3 Update reference ↗
CVE-2026-67357 2 Aug 2026 < 26.7.3 26.7.3 Update reference ↗
CVE-2026-67356 2 Aug 2026 < 26.7.3 26.7.3 Update reference ↗
CVE-2026-67340 1 Aug 2026 < 26.7.2 26.7.2 Update reference ↗
CVE-2026-67344 1 Aug 2026 < 26.7.2 26.7.2 Update reference ↗
CVE-2026-67341 1 Aug 2026 < 26.7.2 26.7.2 Update reference ↗
CVE-2026-67343 1 Aug 2026 < 26.7.2 26.7.2 Update reference ↗
CVE-2026-67342 1 Aug 2026 < 26.7.2 26.7.2 Update reference ↗
CVE-2026-44221 12 May 2026 >= 21.10.1, < 26.4.2 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.