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

Adobe

After Effects

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-48367 14 Jul 2026 ≤ 26.2.1; ≤ 25.6.5 26.3; 25.6.6 Update reference ↗
CVE-2026-48274 14 Jul 2026 ≤ 26.2.1; ≤ 25.6.5 26.3; 25.6.6 Update reference ↗
CVE-2026-34690 12 May 2026 ≤ 26.2.1; ≤ 25.6.5 26.3; 25.6.6 Update reference ↗
CVE-2026-34644 12 May 2026 ≤ 26.0; ≤ 25.6.4 26.2; 25.6.5 Update reference ↗
CVE-2026-34643 12 May 2026 ≤ 26.0; ≤ 25.6.4 26.2; 25.6.5 Update reference ↗
CVE-2026-34642 12 May 2026 ≤ 26.0; ≤ 25.6.4 26.2; 25.6.5 Update reference ↗
CVE-2026-21329 10 Feb 2026 ≤ 25.6 25.6.4; 26.0 Update reference ↗
CVE-2026-21323 10 Feb 2026 ≤ 25.6 25.6.4; 26.0 Update reference ↗
CVE-2026-21324 10 Feb 2026 ≤ 25.6 25.6.4; 26.0 Update reference ↗
CVE-2026-21326 10 Feb 2026 ≤ 25.6 25.6.4; 26.0 Update reference ↗
CVE-2026-21322 10 Feb 2026 ≤ 25.6 25.6.4; 26.0 Update reference ↗
CVE-2026-21318 10 Feb 2026 ≤ 25.6 25.6.4; 26.0 Update reference ↗
CVE-2026-21328 10 Feb 2026 ≤ 25.6 25.6.4; 26.0 Update reference ↗
CVE-2026-21319 10 Feb 2026 ≤ 25.6 25.6.4; 26.0 Update reference ↗
CVE-2026-21350 10 Feb 2026 ≤ 25.6 25.6.4; 26.0 Update reference ↗
CVE-2026-21330 10 Feb 2026 ≤ 25.6 25.6.4; 26.0 Update reference ↗
CVE-2026-21325 10 Feb 2026 ≤ 25.6 25.6.4; 26.0 Update reference ↗
CVE-2026-21327 10 Feb 2026 ≤ 25.6 25.6.4; 26.0 Update reference ↗
CVE-2026-21320 10 Feb 2026 ≤ 25.6 25.6.4; 26.0 Update reference ↗
CVE-2026-21321 10 Feb 2026 ≤ 25.6 25.6.4; 26.0 Update reference ↗
CVE-2026-21351 10 Feb 2026 ≤ 25.6 25.6.4; 26.0 Update reference ↗
CVE-2025-54241 9 Sep 2025 ≤ 24.6.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-54239 9 Sep 2025 ≤ 24.6.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-54240 9 Sep 2025 ≤ 24.6.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-43587 8 Jul 2025 ≤ 24.6.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47109 8 Jul 2025 ≤ 24.6.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-27184 8 Apr 2025 ≤ 24.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-27182 8 Apr 2025 ≤ 24.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-27186 8 Apr 2025 ≤ 24.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-27185 8 Apr 2025 ≤ 24.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-27187 8 Apr 2025 ≤ 24.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-27183 8 Apr 2025 ≤ 24.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-27204 8 Apr 2025 ≤ 24.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-49537 10 Dec 2024 ≤ 25.0.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-47443 12 Nov 2024 ≤ 24.6.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-47441 12 Nov 2024 ≤ 24.6.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-47445 12 Nov 2024 ≤ 24.6.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-47444 12 Nov 2024 ≤ 24.6.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-47442 12 Nov 2024 ≤ 24.6.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-47446 12 Nov 2024 ≤ 24.6.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-39381 13 Sep 2024 ≤ 24.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-39380 13 Sep 2024 ≤ 24.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-41867 13 Sep 2024 ≤ 24.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-39382 13 Sep 2024 ≤ 24.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-41859 13 Sep 2024 ≤ 24.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-20737 10 Apr 2024 ≤ 23.6.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-48633 13 Dec 2023 ≤ 23.6.0 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-2023-48634 13 Dec 2023 ≤ 23.6.0 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-2023-48635 13 Dec 2023 ≤ 23.6.0 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-2023-48632 13 Dec 2023 ≤ 23.6.0 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.