# CVE-2026-101094: Information disclosure in affinity

> Crafted Affinity documents can disclose heap memory or crash the application due to improper UTF-8 handling.

- **Severity:** Low 3.6 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-h877-95q5-3r86

## What is CVE-2026-101094?

CVE-2026-101094 is a low-severity vulnerability in canva affinity, published on 9 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The Affinity by Canva application before 3.3.1 (October 2026 release) did not correctly handle incomplete UTF-8 character sequences when parsing text in Affinity document files, leading to a heap buffer over-read. A threat actor could craft an Affinity document that, when opened by a user in Affinity, could disclose the contents of adjacent heap memory in the document's text or result in an application crash.

Weakness: CWE-126 (Buffer Over-read)

## Which versions are affected by CVE-2026-101094?


## How do I fix CVE-2026-101094?

No fix has been published for CVE-2026-101094 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-101094 being exploited?

There is no known exploitation of CVE-2026-101094 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-101094 and fix it if it is affected.

What it is: CVE-2026-101094 is a low-severity vulnerability in canva affinity, published on 9 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-101094 in the wild and no public exploit code.

Affected product: canva affinity. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-101094/ (Markdown: https://insights.sbomify.com/CVE-2026-101094/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-101094
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-101094
- OSV: https://osv.dev/vulnerability/CVE-2026-101094

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-101094/
Summaries are generated and may contain mistakes; the official description above is the record.