Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-101094 Overview
CVE-2026-101094 is a heap buffer over-read vulnerability in the Affinity by Canva application. Versions prior to 3.3.1, released in October 2026, fail to correctly handle incomplete UTF-8 character sequences when parsing text inside Affinity document files. A threat actor can craft a malicious Affinity document that, when opened by a user, discloses adjacent heap memory contents through the document's text or triggers an application crash. The weakness is tracked under [CWE-126: Buffer Over-read].
Critical Impact
Opening a crafted Affinity document can leak heap memory contents or crash the application, requiring user interaction and local file access.
Affected Products
- Affinity by Canva application versions prior to 3.3.1
- Document parsing component handling UTF-8 encoded text
- Fixed in the October 2026 release (3.3.1)
Discovery Timeline
- 2026-10-09 - CVE CVE-2026-101094 published to NVD
- 2026-10-09 - Last updated in NVD database
Technical Details for CVE-2026-101094
Vulnerability Analysis
The flaw occurs during text parsing inside Affinity document files. When the parser encounters an incomplete multi-byte UTF-8 sequence, it continues reading past the valid boundary of the input buffer. This produces a heap buffer over-read, meaning the parser accesses memory beyond the allocated region holding the document text.
The consequence is twofold. Adjacent heap memory may be interpreted as text and surfaced within the opened document, exposing data from other allocations. Alternatively, the read may touch unmapped memory and crash the Affinity process, producing a denial-of-service condition for the user's editing session.
Exploitation requires a user to open a crafted document locally, which limits scalability but aligns with phishing and supply-of-asset workflows common to creative professionals. Confidentiality impact is bounded by what resides in the heap at the time of parsing.
Root Cause
The root cause is improper validation of UTF-8 byte sequence completeness during text extraction. The parser trusts the declared or implied length of multi-byte characters without verifying that the required continuation bytes remain within the input buffer. A truncated lead byte therefore drives subsequent reads beyond the buffer edge.
Attack Vector
An attacker crafts an Affinity document containing a deliberately truncated UTF-8 sequence at a text boundary. The attacker delivers the document through email, shared storage, or collaboration channels. The victim opens the file in a vulnerable Affinity client, which triggers the over-read during text parsing. Public exploit code is not available, and the vulnerability is not listed in CISA KEV.
No verified exploit code is available. See the Canva Security Trust Information advisory for vendor technical details.
Detection Methods for CVE-2026-101094
Indicators of Compromise
- Affinity application crash events correlated with recently opened .afdesign, .afphoto, or .afpub files from untrusted sources
- Unexpected text artifacts or binary fragments appearing inside opened Affinity documents
- Delivery of Affinity document files via external email or messaging to users without a business justification
Detection Strategies
- Monitor endpoint telemetry for Affinity process crashes immediately following document open events
- Inspect inbound email and file-sharing traffic for Affinity document extensions originating from untrusted senders
- Track Affinity application version inventory to identify endpoints running builds older than 3.3.1
Monitoring Recommendations
- Alert on Affinity process termination with access violation or segmentation fault signatures
- Log file-open events for Affinity document formats and correlate with the source of the file
- Review crash dump collection policies to ensure heap state is captured for post-incident analysis
How to Mitigate CVE-2026-101094
Immediate Actions Required
- Upgrade all Affinity by Canva installations to version 3.3.1 or later
- Instruct users not to open Affinity documents received from untrusted or unverified sources
- Inventory endpoints to identify Affinity clients still running vulnerable builds
Patch Information
Canva addressed the vulnerability in the October 2026 release of Affinity, version 3.3.1. The fix corrects UTF-8 sequence boundary validation during document text parsing. Refer to the Canva Security Trust Information portal for release notes and distribution details.
Workarounds
- Restrict opening of Affinity documents to files sourced from trusted internal repositories
- Isolate document review workflows on non-sensitive workstations until patching is complete
- Enable application crash reporting and endpoint protection on systems handling third-party documents
# Configuration example
# Verify installed Affinity version on macOS
/Applications/Affinity\ Designer\ 2.app/Contents/MacOS/Affinity\ Designer\ 2 --version
# Verify installed Affinity version on Windows (PowerShell)
Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*" |
Where-Object { $_.DisplayName -like "Affinity*" } |
Select-Object DisplayName, DisplayVersion
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

