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

Adobe

Adobe Framemaker

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-27297 14 Apr 2026 ≤ 2022.8 2022.9 Update reference ↗
CVE-2026-27300 14 Apr 2026 ≤ 2022.8 2022.9 Update reference ↗
CVE-2026-27296 14 Apr 2026 ≤ 2022.8 2022.9 Update reference ↗
CVE-2026-27290 14 Apr 2026 ≤ 2022.8 2022.9 Update reference ↗
CVE-2026-27298 14 Apr 2026 ≤ 2022.8 2022.9 Update reference ↗
CVE-2026-27294 14 Apr 2026 ≤ 2022.8 2022.9 Update reference ↗
CVE-2026-27295 14 Apr 2026 ≤ 2022.8 2022.9 Update reference ↗
CVE-2026-27301 14 Apr 2026 ≤ 2022.8 2022.9 Update reference ↗
CVE-2026-27299 14 Apr 2026 ≤ 2022.8 2022.9 Update reference ↗
CVE-2026-27293 14 Apr 2026 ≤ 2022.8 2022.9 Update reference ↗
CVE-2026-27292 14 Apr 2026 ≤ 2022.8 2022.9 Update reference ↗
CVE-2025-54282 14 Oct 2025 ≤ 2022.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-54281 14 Oct 2025 ≤ 2022.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-54233 12 Aug 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-54230 12 Aug 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-54232 12 Aug 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-54231 12 Aug 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-54229 12 Aug 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47120 8 Jul 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47126 8 Jul 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47128 8 Jul 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47131 8 Jul 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47122 8 Jul 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47130 8 Jul 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47133 8 Jul 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47121 8 Jul 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47124 8 Jul 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47127 8 Jul 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47129 8 Jul 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47119 8 Jul 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47125 8 Jul 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47123 8 Jul 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47132 8 Jul 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-30300 8 Apr 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-30303 8 Apr 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-30295 8 Apr 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-30297 8 Apr 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-30304 8 Apr 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-30301 8 Apr 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-30302 8 Apr 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-30299 8 Apr 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-30296 8 Apr 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-30298 8 Apr 2025 ≤ 2022.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-53959 10 Dec 2024 ≤ 2022.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-47425 9 Oct 2024 ≤ 2022.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-47423 9 Oct 2024 ≤ 2022.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-47421 9 Oct 2024 ≤ 2022.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-47424 9 Oct 2024 ≤ 2022.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-47422 9 Oct 2024 ≤ 2022.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-30291 16 May 2024 ≤ 2022.3 No fixed version is explicitly recorded in the structured CVE data. 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.