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

Adobe

Audition

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 audition, 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-47967 14 Jul 2026 ≤ 26.0; ≤ 25.6.4 26.3; 25.6.6 Update reference ↗
CVE-2026-48309 14 Jul 2026 ≤ 26.0; ≤ 25.6.4 26.3; 25.6.6 Update reference ↗
CVE-2026-47969 14 Jul 2026 ≤ 26.0; ≤ 25.6.4 26.3; 25.6.6 Update reference ↗
CVE-2026-48365 14 Jul 2026 ≤ 26.0; ≤ 25.6.4 26.3; 25.6.6 Update reference ↗
CVE-2026-47968 14 Jul 2026 ≤ 26.0; ≤ 25.6.4 26.3; 25.6.6 Update reference ↗
CVE-2026-48368 14 Jul 2026 ≤ 26.0; ≤ 25.6.4 26.3; 25.6.6 Update reference ↗
CVE-2026-21316 10 Feb 2026 ≤ 25.3 25.6; 26.0 Update reference ↗
CVE-2026-21312 10 Feb 2026 ≤ 25.3 25.6; 26.0 Update reference ↗
CVE-2026-21315 10 Feb 2026 ≤ 25.3 25.6; 26.0 Update reference ↗
CVE-2026-21313 10 Feb 2026 ≤ 25.3 25.6; 26.0 Update reference ↗
CVE-2026-21317 10 Feb 2026 ≤ 25.3 25.6; 26.0 Update reference ↗
CVE-2026-21314 10 Feb 2026 ≤ 25.3 25.6; 26.0 Update reference ↗
CVE-2025-43580 8 Jul 2025 ≤ 24.6.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-49536 15 Nov 2024 ≤ 24.4.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-47449 12 Nov 2024 ≤ 24.4.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-41868 11 Sep 2024 ≤ 23.6.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-39378 11 Sep 2024 ≤ 23.6.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-30285 13 Jun 2024 ≤ 23.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-30276 13 Jun 2024 ≤ 23.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-20739 15 Feb 2024 ≤ 23.6.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-47047 16 Nov 2023 ≤ 23.6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-47053 16 Nov 2023 ≤ 23.6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-47046 16 Nov 2023 ≤ 23.6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-47049 16 Nov 2023 ≤ 23.6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-47048 16 Nov 2023 ≤ 23.6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-47050 16 Nov 2023 ≤ 23.6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-47054 16 Nov 2023 ≤ 23.6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-47051 16 Nov 2023 ≤ 23.6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-47052 16 Nov 2023 ≤ 23.6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-40735 16 Mar 2022 unspecified ≤ 14.4; unspecified ≤ None No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-40738 16 Mar 2022 unspecified ≤ 14.4; unspecified ≤ None No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-40742 16 Mar 2022 unspecified ≤ 14.4; unspecified ≤ None No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-40734 16 Mar 2022 unspecified ≤ 14.4; unspecified ≤ None No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-40737 16 Mar 2022 unspecified ≤ 14.4; unspecified ≤ None No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-40740 16 Mar 2022 unspecified ≤ 14.4; unspecified ≤ None No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-40741 16 Mar 2022 unspecified ≤ 14.4; unspecified ≤ None No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-40739 16 Mar 2022 unspecified ≤ 14.4; unspecified ≤ None No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-40736 16 Mar 2022 unspecified ≤ 14.4; unspecified ≤ None No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-44697 20 Dec 2021 unspecified ≤ 14.4; unspecified ≤ 22.0; unspecified ≤ None 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-2021-44698 20 Dec 2021 unspecified ≤ 14.4; unspecified ≤ 22.0; unspecified ≤ None 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-2021-44699 20 Dec 2021 unspecified ≤ 14.4; unspecified ≤ 22.0; unspecified ≤ None 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-2021-36003 19 Nov 2021 unspecified ≤ 14.2; unspecified ≤ None 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.