Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver crafted Affinity document to victim
-
ExploitVictim browses/previews file in Finder
-
ExecutionQuickLook reads image beyond pixel buffer
-
ImpactAdjacent heap memory disclosed in rendered thumbnail
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Buffer over-read prevention
|
| Exploitation Conditions | Exploitation requires that a crafted Affinity document file reside on the victim's macOS system and that the victim view or preview it in Finder, triggering the QuickLook thumbnail/preview extension - the specific vulnerable code path is Affinity's QuickLook thumbnail and preview generation, which fails to validate declared image dimensions against actual pixel-data size. Limiting factors: the attack is local (the malicious file must first reach the host), only affects Affinity for macOS before version 3.3.1, requires the victim to browse to or preview the file, and yields only a non-deterministic read of adjacent heap memory - the attacker cannot choose what is disclosed, which substantially limits reliable data exfiltration. |
| Impact | This is a genuinely low-priority issue despite being a memory-safety bug. The provided CVSS 3.1 vector (AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N) and base score of 2.9 reflect a local attack vector, high attack complexity (heap over-read of adjacent memory is non-deterministic and layout-dependent), and only low confidentiality impact with no integrity or availability impact. There is no EPSS score, no CISA KEV listing, and no public POC referenced - exploitation signal is uniformly weak: no public exploit identified at time of analysis. One internal inconsistency worth noting: the vector sets UI:N, yet the description requires a victim to view or preview the crafted file in Finder, which is at minimum passive user interaction - the UI:N rating hinges on the fact that macOS QuickLook auto-generates thumbnails when a folder is merely browsed, so no explicit click is needed. Also note the vector sets A:N even though the description explicitly states the preview extension can be crashed, which is a (low) availability impact. Net: a legitimate out-of-bounds heap read (CWE-126) that leaks small amounts of adjacent heap memory into a rendered thumbnail, but the local vector, high complexity, information-only impact, and complete absence of exploitation evidence make this a routine patch-on-cycle item, not an urgent one. |
| Exploit ScenarioDerived | An attacker crafts an Affinity document whose declared image dimensions exceed the actual pixel-data buffer and delivers it to a victim (e.g., via download, email attachment, or shared folder). When the victim browses the containing folder or previews the file in macOS Finder, QuickLook generates a thumbnail and reads past the end of the pixel buffer, rendering adjacent heap memory into the preview image or crashing the preview extension. No public exploit code is identified, and the leaked contents are non-deterministic, so practical weaponization for targeted data theft is difficult. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 09, 2026
An out-of-bounds heap read in Affinity by Canva for macOS (before 3.3.1) lets a crafted Affinity document leak adjacent heap memory into the QuickLook thumbnail and preview images rendered by Finder, or crash the thumbnail/preview extension. The attack is local - the malicious file must already reside on the target Mac - and requires the victim to browse to or preview the file in Finder, which triggers the vulnerable code path; the disclosed bytes are non-deterministic, so an attacker cannot select what is exposed. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the assessed severity is low (CVSS 3.1 base 2.9).
RemediationAI
Upgrade Affinity by Canva for macOS to 3.3.1 or later - vendor-released patch: 3.3.1 - as documented in the Canva advisory at https://trust.canva.com?tcuUid=1998378a-9134-47e9-b761-7a49d5fd6bfb; because the fix is a straightforward input-validation change in the QuickLook generator, rollout can follow normal update cadence for a low-severity issue. If immediate patching is not possible, disable the Affinity QuickLook extension so Finder stops invoking the vulnerable preview code path - on macOS Ventura and later via System Settings > General > Login Items & Extensions > Quick Look, or by removing/disabling the Affinity entry in the QuickLook extensions list; the trade-off is loss of Finder thumbnails and previews for Affinity documents for all users on that Mac. Alternatively, treat Affinity documents from untrusted sources as potentially hostile: avoid previewing them in Finder, store them outside indexed/previewed locations, or quarantine them before opening in the full application, accepting that this depends on user behavior and does not scale. Since exploitation also requires an attacker to first place a crafted file on the host, standard endpoint controls (download and email attachment filtering for Affinity document types, restricting untrusted file sharing into user home directories) further reduce exposure, but none of these substitute for the 3.3.1 update.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a buffer over-read (CWE-126) in Affinity's QuickLook thumbnail and preview generation for Affinity document files on macOS. QuickLook extensions run on the previewing user's session to produce Finder icons and previews; Affinity's generator parses embedded image data in the document but fails to validate the declared image dimensions against the actual size of the pixel buffer, so an image whose header claims larger dimensions than the supplied data causes reads past the end of the heap allocation. The resulting thumbnail or preview can therefore contain residual heap contents, but the read is a non-deterministic overrun - the attacker does not control which adjacent bytes are rendered, which greatly limits reliable data exfiltration. The assessed vector (CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:L) confirms a local, high-complexity, unauthenticated attack requiring user interaction, with only low confidentiality impact and a low-integrity/availability impact (the preview extension can crash). The supplied CPE, cpe:2.3:a:canva:affinity:*:*:*:*:*:*:*:*, uses wildcards for version and platform and so cannot by itself distinguish patched from unpatched builds or confirm a macOS-only scope; the macOS limitation comes from the description and the QuickLook-specific attack surface. Failure to render previews, crashes, or memory corruption in the extension process are the main observable effects.
Know when Affinity gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Crafted file must be local and previewed (AV:L, UI:R); heap over-read of adjacent memory is layout-dependent (AC:H); low info leak (C:L) plus documented extension crash (A:L); no privileges needed (PR:N).
Primary rating from Vendor (Canva).
CVSS VectorVendor: Canva
Lifecycle Timeline
1DescriptionCVE.org
The Affinity by Canva application for macOS before 3.3.1 (October 2026 release) did not validate image dimensions against the size of the pixel data when generating QuickLook thumbnails and previews of Affinity document files, leading to an out-of-bounds heap read. A threat actor could craft an Affinity document that, when displayed or previewed by a user in Finder, could disclose the contents of adjacent heap memory in the rendered thumbnail or preview image, or cause the thumbnail or preview extension to crash.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
A type confusion vulnerability in the EMF (Enhanced Metafile) functionality of Canva Affinity allows attackers to achiev
An out-of-bounds write vulnerability in Canva Affinity's EMF file processing allows attackers to achieve code execution
Opening an attacker-crafted Affinity document in Affinity by Canva versions prior to 3.3.0 can trigger a stack-based buf
An out-of-bounds read vulnerability exists in Canva Affinity's EMF (Enhanced Metafile) file processing functionality, al
An out-of-bounds read vulnerability exists in the EMF (Enhanced Metafile) file handling functionality of Canva Affinity,
An out-of-bounds read vulnerability exists in Canva Affinity's EMF (Enhanced Metafile) file parsing functionality, allow
An out-of-bounds read vulnerability exists in the EMF (Enhanced Metafile) file parsing functionality of Canva Affinity,
An out-of-bounds read vulnerability exists in Canva Affinity's EMF (Enhanced Metafile) file handling that allows attacke
An out-of-bounds read vulnerability exists in Canva Affinity's EMF (Enhanced Metafile) file processing functionality, af
An out-of-bounds read vulnerability exists in the EMF (Enhanced Metafile) file parsing functionality of Canva Affinity,
An out-of-bounds read vulnerability exists in Canva Affinity's EMF (Enhanced Metafile) file parsing functionality, affec
An out-of-bounds read vulnerability exists in Canva Affinity's EMF (Enhanced Metafile) file parsing functionality, affec
EUVD-2026-95749
GHSA-5hh5-7xcc-m4cx
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB