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

baptisteArno

typebot.io

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-62865 25 Aug 2026 < 3.18.0 3.18.0. Update reference ↗
CVE-2026-62861 25 Aug 2026 < 3.18.0 3.18.0. Update reference ↗
CVE-2026-62862 25 Aug 2026 < 3.18.0 3.18.0 Update reference ↗
CVE-2026-48763 11 Aug 2026 < 3.17.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-48762 11 Aug 2026 < 3.16.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-48765 11 Aug 2026 < 3.17.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-47705 11 Aug 2026 = 3.16.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-48767 11 Aug 2026 < 3.17.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-48494 11 Aug 2026 = 3.16.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-47704 11 Aug 2026 < 3.17.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-48483 11 Aug 2026 < 3.17.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-48495 11 Aug 2026 < 3.17.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-48766 11 Aug 2026 < 3.17.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-42142 11 Aug 2026 < 3.17.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-47702 11 Aug 2026 = 3.16.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-49213 10 Jul 2026 < 3.17.2 3.17.2. Update reference ↗
CVE-2026-48764 17 Jun 2026 < 3.17.2 3.17.2. Update reference ↗
CVE-2026-48768 17 Jun 2026 < 3.17.0 3.17.0. Update reference ↗
CVE-2026-48759 17 Jun 2026 < 3.16.0 3.16.0. Update reference ↗
CVE-2026-39969 22 May 2026 < 3.17.0 3.17.0. Update reference ↗
CVE-2026-39967 22 May 2026 < 3.16.0 3.16.0. Update reference ↗
CVE-2026-39968 22 May 2026 < 3.16.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-39966 22 May 2026 < 3.16.0 3.16.0. Update reference ↗
CVE-2026-39970 22 May 2026 < 3.16.0 3.16.0. Update reference ↗
CVE-2026-39965 22 May 2026 < 3.16.0 3.16.0. Update reference ↗
CVE-2026-39964 22 May 2026 < 3.16.0 3.16.0. Update reference ↗
CVE-2026-34207 22 May 2026 < 3.16.0 3.16.0. Update reference ↗
CVE-2026-33712 22 May 2026 < 3.16.0 3.16.0. Update reference ↗
CVE-2026-28445 22 May 2026 < 3.16.0 3.16.0. Update reference ↗
CVE-2026-28444 22 May 2026 < 3.16.0 3.15.2. Update reference ↗
CVE-2025-65098 22 Jan 2026 < 3.13.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-64709 13 Nov 2025 < 3.13.1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2025-64706 13 Nov 2025 >= 3.9.0, < 3.13.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-30264 4 Apr 2024 < 2.24.0 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.