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

Canva

Affinity

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 affinity, 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-81546 17 Sep 2026 Affinity: < 3.3.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-66342 17 Mar 2026 3.0.1.3808 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-62500 17 Mar 2026 3.0.1.3808 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-61979 17 Mar 2026 3.0.1.3808 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-64733 17 Mar 2026 3.0.1.3808 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-66000 17 Mar 2026 3.0.1.3808 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-64301 17 Mar 2026 3.0.1.3808 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-64776 17 Mar 2026 3.0.1.3808 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-64735 17 Mar 2026 3.0.1.3808 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-66633 17 Mar 2026 3.0.1.3808 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-58427 17 Mar 2026 3.0.1.3808 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-66617 17 Mar 2026 3.0.1.3808 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47873 17 Mar 2026 3.0.1.3808 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-61952 17 Mar 2026 3.0.1.3808 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-66503 17 Mar 2026 3.0.1.3808 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-66042 17 Mar 2026 3.0.1.3808 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-65119 17 Mar 2026 3.0.1.3808 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-62403 17 Mar 2026 3.0.1.3808 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-20726 17 Mar 2026 3.0.1.3808 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-22882 17 Mar 2026 3.0.1.3808 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.