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

frangoteam

FUXA

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-67442 18 Aug 2026 < 1.3.3 1.3.3. Update reference ↗
CVE-2026-65984 18 Aug 2026 < 1.3.3 1.3.3. Update reference ↗
CVE-2026-67443 18 Aug 2026 < 1.3.3 1.3.3. Update reference ↗
CVE-2026-65985 18 Aug 2026 < 1.3.3 1.3.3. Update reference ↗
CVE-2026-67440 18 Aug 2026 < 1.3.3 1.3.3. Update reference ↗
CVE-2026-47721 18 Aug 2026 < 1.3.2 1.3.2. Update reference ↗
CVE-2026-47719 18 Aug 2026 < 1.3.2 1.3.2. Update reference ↗
CVE-2026-47720 18 Aug 2026 < 1.3.2 1.3.2. Update reference ↗
CVE-2026-47718 12 Aug 2026 FUXA: = 1.3.0-2773 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-47717 12 Aug 2026 FUXA: = 1.3.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-72586 10 Aug 2026 ≤ 1.3.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-43947 21 Jul 2026 = 1.3.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-43946 21 Jul 2026 = 1.3.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-43945 21 Jul 2026 >= 1.2.11, < 1.3.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-25895 9 Feb 2026 < 1.2.10 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-2026-25894 9 Feb 2026 < 1.2.10 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-2026-25893 9 Feb 2026 < 1.2.10 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-2026-25951 9 Feb 2026 < 1.2.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-2026-25939 9 Feb 2026 < 1.2.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-2026-25938 9 Feb 2026 >= 1.2.8, < 1.2.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-2026-25751 6 Feb 2026 < 1.2.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-25752 6 Feb 2026 < 1.2.10 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.