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

Axiomatic

Bento4

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

Official registry publication history is available at bento4, but registry activity is not a publisher support boundary.

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-5236 31 Mar 2026 1.6.0-641 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-5235 31 Mar 2026 1.6.0-641 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-8537 5 Aug 2025 1.6.0-641 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-0870 30 Jan 2025 1.6.0-641 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-0753 27 Jan 2025 1.0; 1.1; 1.2; 1.3; 1.4; 1.5; 1.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-0751 27 Jan 2025 1.0; 1.1; 1.2; 1.3; 1.4; 1.5; 1.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-4584 17 Dec 2022 1.6.0-639 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-3974 13 Nov 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-3817 1 Nov 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-3816 1 Nov 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-3815 1 Nov 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-3814 1 Nov 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-3813 1 Nov 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-3812 1 Nov 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-3810 1 Nov 2022 n/a 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-2022-3809 1 Nov 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-3807 1 Nov 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-3785 31 Oct 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-3784 31 Oct 2022 5e7bb34 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-3670 26 Oct 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-3669 26 Oct 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-3668 26 Oct 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-3667 26 Oct 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-3666 26 Oct 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-3665 26 Oct 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-3664 26 Oct 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-3663 26 Oct 2022 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-3662 26 Oct 2022 n/a 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.