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

Allegra

Allegra

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-11443 12 Jun 2026 8.1.6.22 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-11442 12 Jun 2026 8.1.10.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-11466 29 Oct 2025 8.1.3.32 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-6216 21 Jun 2025 8.1.3.32 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-3485 6 Jun 2025 8.1.1.49 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-3486 22 May 2025 8.1.1.49 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-5581 22 Nov 2024 7.5.1.9 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-5580 22 Nov 2024 7.5.1.9 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-5579 22 Nov 2024 7.5.1.9 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-30372 22 Nov 2024 7.5.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-52334 22 Nov 2024 7.5.0 build 29 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-52333 22 Nov 2024 7.5.0 build 29 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-52332 22 Nov 2024 7.5.0 build 29 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-51648 22 Nov 2024 7.5.0 build 29 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-51647 22 Nov 2024 7.5.0 build 29 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-51646 22 Nov 2024 7.5.0 build 29 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-51645 22 Nov 2024 7.5.0 build 29 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-51644 22 Nov 2024 7.5.0 build 29 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-51643 22 Nov 2024 7.5.0 build 29 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-51642 22 Nov 2024 7.5.0 build 29 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-51641 22 Nov 2024 7.5.0 build 29 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-51640 22 Nov 2024 7.5.0 build 29 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-51639 22 Nov 2024 7.5.0.24 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-51638 22 Nov 2024 7.5.0.24 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.