Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious Affinity document with malformed raster data
-
DeliveryDeliver file to victim via email or download
-
ExploitUser opens document in vulnerable Affinity
-
ExecutionTrigger out-of-bounds read and untrusted pointer dereference
-
ImpactApplication crash or memory corruption
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Array index validation
|
| Exploitation Conditions | Exploitation requires a victim to open a maliciously crafted Affinity document (containing malformed raster image data) in the Affinity application at a version before 3.3.1; there is no network or remote trigger. Limiting factors are significant: the vector is local/file-based (AV:L), it requires user interaction to open the attacker-supplied file (UI:R), and attack complexity is high (AC:H) because the malformed raster data must reliably drive the out-of-bounds read and pointer dereference across variable memory conditions. No special product configuration is needed beyond having a vulnerable Affinity build installed and processing the untrusted document; patched builds (3.3.1 and later) are not affected. |
| Impact | This is a genuinely low-to-moderate priority issue despite being a memory-safety bug. The CVSS 3.1 vector (AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L, base 4.5/Medium) describes a client-side, file-parsing vulnerability: the attacker has no network path (AV:L), must win against high attack complexity (AC:H) - crafting a document whose raster data lands the out-of-bounds read and untrusted-pointer dereference in an exploitable state - and must convince a user to open the file (UI:R). Impact is uniformly Low across confidentiality, integrity and availability, consistent with an OOB read that most realistically yields a crash or limited memory disclosure rather than reliable code execution. No EPSS score, CISA KEV listing, or public POC was provided in the input, so there is no signal of active or probable exploitation - exploitation status is best described as no public exploit identified at time of analysis. The SSVC picture is therefore benign: exploitation not observed, not automatable (each victim must manually open a document), and only partial technical impact. The signals are internally consistent - there is no CVSS-vs-description conflict here - so this reads as a legitimately modest desktop file-parser bug, not a high-urgency flaw. The only caveat is sourcing: the single reference is a Canva trust-portal link rather than a detailed advisory, so independent corroboration of the fix is limited. |
| Exploit ScenarioDerived | A threat actor crafts a malicious Affinity document with malformed raster image data and distributes it via email attachment, a shared project file, or a download, relying on social engineering to get a designer to open it. When opened in a vulnerable Affinity build (before 3.3.1), the parser performs an out-of-bounds read and dereferences an untrusted pointer, producing an application crash or memory corruption. No public exploit code was identified in the provided data, and the high attack complexity (AC:H) makes reliable weaponization beyond a crash non-trivial. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 09, 2026
Opening a maliciously crafted Affinity document in Affinity by Canva builds prior to 3.3.1 can trigger an out-of-bounds read and dereference of an untrusted pointer, resulting in memory corruption or an application crash. Exploitation is file-based and local rather than remote: a victim must open the attacker-supplied document (UI:R) and the malformed raster data must reliably drive the fault across variable memory conditions, making attack complexity high and yielding only a CVSS 3.1 base score of 4.5 (AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L). No public exploit code exists and the issue is not confirmed actively exploited (it does not appear on CISA KEV); our assessment rates this a genuinely low-to-moderate priority memory-safety defect.
RemediationAI
Vendor-released patch: upgrade Affinity by Canva to 3.3.1 (October 2026 release) or later, which corrects the inadequate bounds checking in the raster image parsing path; there is no separate hotfix and no supported path to harden pre-3.3.1 builds in place, so the upgrade is the only definitive fix. Until upgrades can be rolled out, the practical compensating control is to stop treating Affinity documents as inherently trusted: block or quarantine Affinity file attachments at email and web gateways, forbid opening documents from untrusted or unexpected sources, and open unavoidable untrusted files inside a low-privilege, sandboxed or virtualized environment to contain any crash or memory corruption - the trade-off is reduced workflow convenience and imperfect enforcement for a user-driven desktop action. Since the vector is local and file-based with no network component, there is no firewall rule or port restriction that meaningfully reduces exposure, and generic OS hardening yields limited benefit compared with simply not opening the malicious file. Details and confirmation of the patched release are at https://trust.canva.com?tcuUid=1998378a-9134-47e9-b761-7a49d5fd6bfb
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 sits in the raster image parsing path of the Affinity document format, which embeds raster layers alongside vector and text content. When Affinity loads such a document, it reads dimensions, offsets and related metadata from the file and uses those attacker-controlled values to index into heap buffers without validating them against the actual allocated buffer size - the root-cause class recorded is CWE-129 (Improper Validation of Array Index), which here manifests as an out-of-bounds read that can return an attacker-influenced pointer value that the application then dereferences. The result is memory corruption or a crash rather than a guaranteed exploitable primitive, consistent with the limited C:L/I:L/A:L impact ratings and the unchanged scope. The attack surface is entirely local (AV:L): the parser only processes file content when the user opens a document, there is no network listener or remote trigger, no privileges are required to trigger the fault (PR:N), and no non-default product configuration is needed beyond running a vulnerable build. Patched builds 3.3.1 and later are not affected.
Know when Canva 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:R/S:U/C:L/I:L/A:L
File must be opened locally by a user (AV:L, UI:R) and the crafted raster data must hit exploitable memory conditions (AC:H); no auth needed (PR:N) and an OOB read yields only Low C/I/A, mostly a crash.
Primary rating from Vendor (61adb53e-e4b3-47f7-8a93-4717c9e77dc6).
CVSS VectorVendor: 61adb53e-e4b3-47f7-8a93-4717c9e77dc6
Lifecycle Timeline
1DescriptionCVE.org
The Affinity by Canva application before 3.3.1 (October 2026 release) did not perform adequate bounds checking when parsing raster image data in Affinity document files, leading to an out-of-bounds read and the dereference of an untrusted pointer. A threat actor could craft an Affinity document that, when opened by a user in Affinity, could result in memory corruption or an application 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.
Session hijacking in the Canva Android App before 2.376.0 lets an attacker-controlled web page interact with the Canva a
Session hijacking in the Canva Android App before version 2.376.0 arises from an unrestricted header-reflection flaw in
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,
EUVD-2026-95754
GHSA-42j6-qg67-fpwc
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB