Skip to main content
Vulnerability Database/CVE-2026-101130

CVE-2026-101130: Affinity by Canva Heap Buffer Over-Read

CVE-2026-101130 is a heap buffer over-read flaw in Affinity by Canva that allows attackers to disclose memory contents or crash the application. This post covers technical details, affected versions, and mitigation steps.

Published:

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-101130 Overview

CVE-2026-101130 is a heap buffer over-read vulnerability in the Affinity by Canva application prior to version 3.3.1 (October 2026 release). The flaw stems from inadequate bounds checking when parsing arrays of strings inside Affinity document files. A threat actor can craft a malicious Affinity document that, when opened by a victim, discloses adjacent heap memory in the document's text or triggers an application crash. The vulnerability is categorized under CWE-126: Buffer Over-read.

Critical Impact

Opening a crafted Affinity document can leak adjacent heap memory contents into rendered text or crash the application, enabling limited information disclosure and denial of service.

Affected Products

  • Affinity by Canva application versions prior to 3.3.1
  • Fixed in Affinity 3.3.1 (October 2026 release)
  • Document parser handling arrays of strings in Affinity file formats

Discovery Timeline

  • 2026-10-09 - CVE CVE-2026-101130 published to NVD
  • 2026-10-09 - Last updated in NVD database

Technical Details for CVE-2026-101130

Vulnerability Analysis

The vulnerability resides in the Affinity document parser's handling of string arrays. When the parser reads a serialized array of strings, it fails to validate declared lengths against the actual bounds of the allocated heap buffer. Reads beyond the buffer boundary return adjacent heap memory, which may then be rendered inside the document's text layer or trigger a fault in the application. Exploitation requires local user interaction, as the victim must open a maliciously crafted Affinity file. The impact is limited to partial information disclosure and application crashes rather than code execution.

Root Cause

The root cause is missing or insufficient bounds validation [CWE-126] during deserialization of string array structures in Affinity document files. The parser trusts length or count fields embedded in the file without cross-checking them against the actual size of the allocated buffer. Consequently, read operations extend past the end of the heap allocation and return whatever data resides in neighboring memory regions.

Attack Vector

An attacker crafts a malicious Affinity document with manipulated string array metadata and delivers it through email, file sharing, or a web download. When a user opens the file in a vulnerable Affinity client, the parser performs the out-of-bounds read. Disclosed memory may appear in document text fields visible to the user, where it could be exfiltrated by the attacker if the file is later returned, shared, or published. Alternatively, the over-read can land on unmapped memory and crash the application.

No verified public proof-of-concept code is available for this issue. See the Canva Trust Page for vendor details.

Detection Methods for CVE-2026-101130

Indicators of Compromise

  • Unexpected Affinity application crashes correlated with opening third-party or externally sourced document files.
  • Affinity documents containing unexplained binary fragments, non-printable characters, or memory-like artifacts rendered as text.
  • Receipt of Affinity files (.afdesign, .afpub, .afphoto) from untrusted email senders or file-sharing links.

Detection Strategies

  • Monitor endpoint telemetry for Affinity process crashes and faulting module events around document open operations.
  • Hunt for Affinity document files originating from external sources that have unusually large or malformed string array structures.
  • Correlate user reports of garbled or corrupted text in opened documents with recent file receipt from untrusted sources.

Monitoring Recommendations

  • Log Affinity application version inventory across endpoints and flag any version earlier than 3.3.1.
  • Alert on repeated crashes of the Affinity process within short time windows on a single endpoint.
  • Capture file provenance metadata (mark-of-the-web, download source) for Affinity documents entering the environment.

How to Mitigate CVE-2026-101130

Immediate Actions Required

  • Upgrade all Affinity by Canva installations to version 3.3.1 (October 2026 release) or later.
  • Instruct users not to open Affinity documents received from untrusted or unverified sources.
  • Inventory endpoints running Affinity and prioritize patching for systems that handle externally sourced design files.

Patch Information

Canva addressed the vulnerability in Affinity 3.3.1, released in October 2026. The fix introduces bounds checking during string array parsing in the document loader. Refer to the Canva Trust Page for official vendor guidance and release notes.

Workarounds

  • Restrict opening of Affinity documents to files originating from known, trusted authors until patching completes.
  • Open suspect Affinity files inside an isolated virtual machine or sandboxed user profile with no access to sensitive data.
  • Apply application allowlisting and mark-of-the-web enforcement to block or warn on Affinity files downloaded from the internet.

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.