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

FlowiseAI

Flowise

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-30820 7 Mar 2026 < 3.0.13 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-34267 14 Oct 2025 Flowise: 3.0.1 ≤ 3.0.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-61913 8 Oct 2025 Flowise: < 3.0.8 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-2025-61687 6 Oct 2025 Flowise: = 3.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-50538 6 Oct 2025 Flowise: < 3.0.5 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-2025-29192 6 Oct 2025 Flowise: < 3.0.5 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-2025-59528 22 Sep 2025 = 3.0.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-59527 22 Sep 2025 Flowise: = 3.0.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-59434 22 Sep 2025 Flowise: < cloud-hosted (as of Aug 2025) No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-58434 12 Sep 2025 Flowise: <= 3.0.5 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-2024-8181 27 Aug 2024 1.8.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8182 27 Aug 2024 1.8.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-37146 1 Jul 2024 <= 1.4.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-37145 1 Jul 2024 <= 1.4.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-36423 1 Jul 2024 <= 1.4.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-36422 1 Jul 2024 <= 1.4.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-36421 1 Jul 2024 <= 1.4.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-36420 1 Jul 2024 <= 1.4.3 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.